OneStream Excel Enhancement Requests
Hello, Our Organization is currently going through a Planning implementation of OneStream. We have provided a list of enhancement requests to OneStream that we feel would significantly improve the products reporting capabilities. Here is a list of the enhancement requests submitted. I am posting with hope that other customers would also benefit from these enhancements and reach out to OneStream directly to also request this functionality! You can also like ("Kudos") this post. 1. Drill Down within XFGetCell Function. (This was something that came up a lot at Splash when discussing with other customers) 2. Retain excel formatting when refreshing quick views 3. Ability to utilize the member description to pull quick views or XF functions (Today you can only user member name) 4. “Hardcode” the default Quick View POV when creating a new quick view (Users are required to retype their defaults when sending a report to a user otherwise the data could change depending on the other users POV settings) 5. Option for a Default “Member Expansion” that will only pull parent members (Subtotals). This would be helpful when drilling or creating reports
Using Git or other version control source control for OneStream
Has anyone used Git or another version control / source control system with OneStream? Currently, we keep a lot of commented out code in our OneStream system. It would be a lot nicer to be able to only have to keep the latest in production, and have a version control system track the changes. By default ( not that I know how to change it) the OneStream app does only 1 XML document per type, so the changes aren't tracked at the individual object level, and you'll get a lot of changes to search through. Has anyone made it work, or are you aware of a best practices document or other doc for this?
Task Scheduler: best way to disable all tasks in app copies
Hello! When we create a new DEV app copied from our PROD app, the Task Scheduler jobs need to all be disabled in the new DEV app. We have a static text file that we load which generally works fine but we need to remember to keep that file up to date as we add new tasks. Does anyone have a good way to disable all tasks? I don't necessarily want to delete them in case that's what we're testing in the DEV app but I'm open to hearing any suggestions you may have. Thanks, Nicole
Using a Where Clause for the Member Filter Tree - Is this Possible?
Is it possible to use the where clause for the member expansion ".Tree", specifically filtering on the AccountDim. There is a top-level reporting cube and a few merged cubes sitting beneath (using entity extensibility). There are also a number of extensible Account Dimensions utilized... i.e., Level 1 (Highest - Forecast Accounts) Level 2 (Consolidated Accounts) Level 3 - #1 (Lowest - linked to lower-level reporting subsidiary cubes using base GL Accounts - the account dimension names for these cubes always include 'Base') Level 3 - #2 (base GL Accounts) Level 3 - #3 (base GL Accounts) Level 3 - #4 (base GL Accounts) I am looking to build a report using the ".tree" member filter to allow for expandable/collapsible rows (accounts as rows), however I do not want to include the Level 3 Account Dimensions. When building out a consolidating report (pulling from the top-level reporting cube) with the entities running across the columns I am having trouble filtering out the Level 3 Account Dimensions. When I try A#Revenue.Tree.Where(MemberDim DOESNOTCONTAIN 'Base') or something of the similar the report is only displaying the Revenue account. I have tried using the options function such as, A#Revenue.tree.options(Cube=[Top Level Cube], ScenarioType=Actual, MergeMembersFromReferencedCubes=FALSE), however when the merged entities are included in the columns the report pulls in the level 3 account dimensions.. Ultimately the goal is to create a report that allows for expandable/collapsible account rows but filters out the level 3 account dimensions. Any ideas how to achieve this?
SQL table editor - no access to add or delete rows
Hi, As an admin user I can add and delete rows from a SQL table editor. However a non-admin user does not have access to do so. They can view the data but the add/delete row button on the toolbar are greyed out. Can someone tell me how to give them access to add/delete rows? Thank you MarkHow to Run Workspace Assembly from a Data Management Step In 6 Easy Steps
This was originally a question.It took a while to figure out, so to save someone else the hours of trial and error, here is the process I use in detail, start to finish, to run a Workspace-based Data Management step in a Workspace Assembly business rule. Here's a How-to step by step: List of abbreviations used below: DM: Data Management WS: Workspace MU: Maintenance Unit BR: Business Rule AS: Assembly 1. Workspace:Set the NameSpace Prefix - this is what gets filled in at runtime for __WSNameSpacePrefix 2. Assemblies: Note these properties 3. Create the Assembly Business Rule:Create an "Extender" business rule, this is done by right clicking files and selecting "Extensibility Rules" Add some test code, to verify correct configuration, such as BRApi.ErrorLog.LogMessage(si, "Hello from the new extender!"then code the way you would any other extender 4. Create The Data Management Group: Create a DataManagement Group in the same workspace that the Assembly that has your business rule is in 5. Create a Data Management Step - Create a DM step in the new DM Group, reference the rule using the pattern: Workspace.{WorkspacePrefix}.{AssemblyName}.{BusinessRuleName} In this case it would be: Workspace.Current.DMTestAS.DMTestStepExtender Note: we could also use 'DMTestWS' instead of 'Current'.We use Current because the DM Step is in the same WS as the Extender Rule. 7. Done! Test the DM Step with run button and check the error log(System Tab -> Logging -> Error Log),for your test code's output.O#Forms submissions to locked forecast scenarios
Hi all, How do you handle preventing users from accidentally loading data via an excel XFSetCell or QV submission to O#Forms/O#BeforeAdj on a scenario that’s locked on the workflow in OS? I’ve submitted this via OS support and there’s an enhancement request for “Requesting option to prevent users from submitting data in Excel via XFsetcell or QuickView” but there’s no workaround that they can provide. Our FP&A users load all data via excel and they’re generally educated enough to know what dimensions to change, but sometimes the communication doesn’t go out timely enough from corporate FP&A to stop loading adjustments (though the scenario is locked promptly on the workflow) and so we run into this issue. Any thoughts or feedback would be welcomed! Thanks!
