The errors that you are seeing reflect the rule being used as Finance
Business Rule instead of an XFBR, I recently replied to this post with
an updated version of the business rule (as a finance business rule);
however, my response was "rejected by a...
No worries. The error message is due to the business rule type. You are
calculating via a Finance business rule; however, the provided code
snippet is for an XFBR. You will obviously need to update this code to
fit your specific application, but hope...
Depending on the complexity of the requirement, you could also use
parameters and XFBRs on the rows/columns to make the relationships more
dynamic. For example, you could pass XFBR(XfbrRuleName, FunctionName,
firstUd1=|!prm_SelectMember1!|, secondUd1...
Hello, I am receiving a similar error message when trying to utilize
nested parameters for cube view formatting. The cube view renders
properly when it is run directly; however, when the cube view is run
from a workflow form, the following error mess...
