SetLiteralParameterValue issue on web
In our first workflow step, we set the value of a literal parm using dashboard extender and then in next step use that parm in a DM job to export data based on that parm value. On windows client, our DM job works fine but when we try it on web, it does not find the value of the parm and errors out. Can someone please share any experience with this kind of setup and how to make it work on web?
Process around InUse flag for master data
What do you use as guidelines to flip the "inuse" flag on accounts or entities? Do you wait until the entity balances are brought to zero in your source or some other trigger? What considerations do you make around any immaterial translation values? Interested to hear what your company is doing - thanks so much! -Nicole
How to Add Adjustments with Add Back Category and Free-Form Add Back Name to Actuals in OneStream?
Hi Everyone, I’m working with Actuals data structured like the attached screenshot and want to add adjustments linked to this data. Key points: Adjustments must tie to Actuals by Company, Account, and Month Each adjustment includes: An Add Back Category An Add Back Name, which is free-form text and can vary monthly I want to maintain monthly detail and enable reporting and drill-down by both Add Back Category and Add Back Name My questions: What’s the best approach to model and load adjustments with both a Add Back Category and a free-form Add Back Name in OneStream? Should Add Back Name be a UD member with auto-create, a text attribute, or something else? How to avoid member explosion or reporting complexity given the free-form nature of Add Back Name? How can I ensure adjustments roll up correctly and maintain data integrity? Any recommendations for validation, governance, and reporting for this kind of adjustment detail? Thanks in advance for your insights!
