v9 - Linked Reporting Parameters not working
We have a dashboard that was originally built in v7 that allows us to add an intersection of data to a CV . When you click on an intersection in the CV, the code takes the Linked Parameters from the CV and populates combo boxes with the members in the intersection. You then change one or more of the members in the combo boxes and click another button to add this intersection (by adding a penny to another account) which then shows up in the CV. This used to work in v7 but now as we are testing this in v9 the linked parameters that are being passed to the code are not the current values in the intersection you are on. It seems to be passing old values. Any thoughts?
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!
How to stop a Data Adapter task that keeps launching CubeViews?
Hello, I’m facing an issue with a Data Adapter that launches a CubeView. The problem is that the Data Adapter seems to be looping and triggering the CubeView multiple times, which results in a very long execution time. When I manually cancel some of the tasks related to the CubeView, it looks like new tasks keep getting created, as if the main process is still running. My question is: Is there a way to kill or stop the main task/process that was initiated by the Data Adapter, so that all dependent CubeView tasks are also stopped as a consequence? Or is there a recommended way to safely terminate this kind of runaway Data Adapter execution PS : The same OS environment hosts both development and production. I’m currently running OneStream version 7.2. Thanks in advance for your help.Extract Related components for Dashboard
Hi OneStream experts, Lets say a dashboard has 10 components in DEV and in PROD. Added 11th component in DEV and want to move it to PROD by Extract and Load. Is there any easy way to collect all related components of a dashboard? Manually collecting components is painful. What is the best secured way to collecting objects to move it to PROD? Thanks //SureshCentering Dashboard Within a Dashboard
Here's the scenario I'm trying to figure out: My main dashboard has 3 columns which contain 3 different dashboards. The left and right dashboards are just for navigation and have a set width. I want the middle dashboard to be center aligned with the available space left over after the left and right dashboards are populated. Basically I'm trying to design the dashboard so that it's readable from a laptop screen but on a normal monitor I want the main section of the dashboard (the middle) to fill in all of the empty space and center align horizontally. I hope that makes sense? Thanks, Brandon
Transaction Matching Module movement to different environment
We are preparing to move the Transaction Matching (TM) module, an out-of-the-box marketplace solution, from the Development environment to the QAT environment. Could someone please guide me on the process for migrating the database tables, along with the match sets and matching rules created within the TM module? Specifically, is there a way to extract and load these artifacts directly, rather than recreating the entire solution from scratch in the new environment?
