Hi Mathias,Thank you for your feedback. The FTP class is only a test class. I take it using the Person and Group functionality does not stop the Doc Class appearing in the LOV?ThanksMiguel
@Mathias Dahl , thank you.Is this possible in a different UPD in IFS10? or only available in IFS Cloud?Miguel
@Mathias Dahl , sorry forgot to ask. Is it the limit 20 documents in the Card view ?Thanks
Hi @CallumW ,Excellent, that has worked !, many thanksMiguel
@CallumW , do you know if there are any install scripts or server configurations we can apply to automate this change? it would be easier if we just centrally apply this rather than have everyone do manually. Many thanksMiguel
Hi @Link Thank you for your email. I am looking to use the property field definition rather than creating a custom field in this case. So, I just wanted to make sure that my definitions in this window are correct.Kind regards
Hi @Link Many thanks, that makes sense.Could you please let me know if you see anything wrong with my syntax for the condition/filter below?UPPER('$PROJECT_ID$')UPPER('$SUB_PROJECT_ID$')At the moment this syntax is not working for me in the lobby where these parameters are passed to the lobby element linked to this info sourceMiguel
Hi @Link Thank you, yes I tested and it does not return any values.I would be surprise if there is no way to pass parameters from the Lobby header to a Lobby Element that uses a Data Source type Info Source. Surely this is possible somehow.I think your suggestion is a good one, and I think the syntax is just not right. I don’t get an error message so I don’t think we are barking to the wrong tree ;-)Miguel
@Link if I type values for the parameter, keeping the filters, I just get an empty table, please see screenshot.So no error messageMiguel
@Link , I have solved this, as I was guessing it was the syntax at the filter level. The syntax below has worked like a gem ;-) $PROJECT_ID$$SUB_PROJECT_ID$
@Link hardcoding values in the column value is standard functionality and yes that works, but been able to pass a parameter is more interesting. As I said changing the syntaxes of the parameterised value has worked for me. Many thanks for your initial input.
Hi @Bhagya Wickramasinghe ,Your pointer was very useful. I modified the angle of the solution and the design shown below is now working for me. The permission set NP_CM_L1_AWARD allows for RMB Award Sales Contract, however the customer event below limit this authority to only to the lowest Category (L1).Many thanks Miguel
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.