Hi all,
could you confirm that it is not possible to use %CATEGORY_SET% in a *SELECT statement when the logic is incluced in the Default logic?
For example, this kind of syntax doesn't work in Default Logic but it works fine when It is executed by a package:
*SELECT(%MY_TIME%,"ID","TIME","ID='%TIME_SET%'")
In this case, what kind of workaround is possible?
thanks for your help,
Romuald
Hi Romuald,
You dont need this in the default logic. The default logic automatically restricts the whole logic based on the CV. On the other hand, the other scripts doesnt do this. Thats why, we send the members through DIMENSION_SET variable to restrict the scope of the logic.
In the default, you dont have to use %TIME_SET%. The logic will automatically work on the time member selected in your CV.
Hope this helps.
Hi,
indeed my example wasn't relevant. Here is a good example:
*SELECT(%PREVCATEGORY%,"PREVIOUS_CATEGORY","CATEGORY","ID = '%CATEOGRY_SET%' ")
*XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%, %PREVCATEGORY%
I use it to add the previous category defined in PREVIOUS_CATEGORY property.
regards,
Romuald
OK but I how can I restrict my SELECT statement to the category provided by the CV?
The following SQL syntax can not be used in Default logic:
*SELECT(%PREVCATEGORY%,"PREVIOUS_CATEGORY","CATEGORY","ID = '%CATEGORY_SET%' ")
I imagine that we have the same problem for MDX syntax. Could you detail the approach using %DIMENSIONNAME%.Properties("%PROPERTYNAME%")
thanks for your help,
Romuald
Does it work if I have more than one category in my CV?
I don't need to use SELECT statement, just to add %PREVCATEGORY% = CATEGORY.CurrentMember.Properties("PREVIOUS_CATEGORY")in my logic?
regards,
Romuald
When you use an input schedule to input data on both ACTUAL and BUDGET data, the %CATEGORY_SET% used in Default logic is ACTUAL,BUDGET. In this case you have more than one category. Is there a MDX syntax to handle this case?
regards,
Romuald
Add a comment