0Using a variable as a field expression in functions
I would like to use a variable as a parameter in functions that take a field expression if possible.
For instance, the following syntax works.
inList(SALES.COUNTRIES.COUNTRY_NAME, $country_list)I would like to use a session variable that would contain "SALES.COUNTRIES.COUNTRY_NAME", i.e. something like this.
inList($field, $country_list)This syntax does not work as expected. The function checks if "SALES.COUNTRIES.COUNTRY_NAME" string is in $country_list, it does not check the value of the SALES.COUNTRIES.COUNTRY_NAME field.
Is there a way to let Incorta know that $field should be interpreted as a field expression/reference and not as the actual string value?
-
Vlad Kaminsky I will work to double check this with our engineering team, but I strongly suspect the inList() function wasn't built to have the first input parameterized.
-
Dan Brock Thanks Dan. For instance, there is the @ operator in PeopleSoft, that converts a string storing a definition reference into the definition.
https://docs.oracle.com/cd/E41633_01/pt853pbh1/eng/pt/tpcd/concept_Operators-074b1b.html
I assumed there could be something similar in Incorta. I have reviewed the documentation but could not find it though, so I hoped maybe I missed it.
-
-
The first argument of inList should be a possible value of a country, not the name of the column. It performs a if the value is in the list of the 2nd value.
Hope this helps
-
I guess that you would like to evaluate different columns based on the login user? We can use CASE statement to accomplish this:
CASE($user='user1',
inList(SALES.COUNTRIES.COUNTRY_NAME, $country_list),$user='user2',inList(SALES.COUNTRIES.COUNTRY_NAME, $country_list), 1=0)-
Dylan Thanks for the idea, Dylan. The first parameter is a field expression in Incorta terms. I ultimately wanted to put the schema name in a variable.
-
