The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
HeatherB_Finit
3 years agoContributor III
Question about Complex Expressions built on Connector Data Sources
When building a Data Source bound to a Connector business rule, if a need arises to use a Complex Expression, and that expression requires referencing several unbound fields, what is the proper state...
JackLacava
OneStream Employee
3 years agoTechnically the separator is ", " (comma and space), so maybe try that. Obviously this doesn't solve the problem if your value contains that same string. Generally speaking, when you drop on args.Line it becomes hack-territory, so chances that things will break somewhere are high.
An alternative approach could be to map that extra field to a spare UD (if you have it), so you can reference it in a Conditional Rule from the transformation rule of the dimension you're writing the expression for; all the UD values could then transform to None with a wildcard mask.
Related Content
- 9 months ago
- 2 years ago
- 1 year ago