Database space control policies
Hi! We are trying to control the size increase in our production application. We know the growth comes from: Stage tables that allow users to drill down and back onto source data. Data records Audit tables (they can grow a lots if they are recording continuous changes to rules, data for example) Logs which will impact Framework database growth (task activity and error logs, will vary depending on the detail login set in BR, DM and on the system configuration as well as your retention policy) Load transactional data, which will increate your data units and data records unnececarily, which BIBlend should be used for this type of data load instead of loading it to the finance cube. We have analyzed it and we realized the StageAttributeTable and other stage tables has a significant size. Has ayone performed databse maintenance by deleting data from the stage tables? Is it possible to do that while keeping the cube data intact and workflows completed? Any ideas or best practices regarding database maintenance would be very welcome. Regards, Xavi
How do I change a parameter value in a dashboard?
Hi everyone, I have a business rules that is triggered through a dashboard. This Business rule is looking at a True/False parameter. How do I add the parameter to the dashboard and with a dropdown list showing the valid values (true/false) that can be used to save the value to the parameter? Thanks in advance,Cube | Data Access | Data Cell Access Security/Slice Security by U1#Geography
Data Management Access Security Please share your expertise to set up a Cube's Data Cell Access Security / Slice Security to limit data read access as outlined below: Dimension: U1# - Geography Total_Geography = Child 1 + Child 2 = Total / Top North_America = Child 1 / NA International = Child 2 / Int'l Slice Security: Access Level - Read Data by Geography - in a CV and a QV Total_Geo_Data = Read Total data | Read NA data and Read Intl data NA_Data = Read NA data | no data access = International and Total Intl_Data = Read Int'l data | no data access = North America and Total TY for your practical advice - SMEs.
Management vs Stat reporting - best practice approach?
Hello, We want to review both our Management and Stat reporting on a monthly basis. The 2 approaches we are considering using are: employ an Audit / Nature UD to build the separate views by adjustments layered over the local GAAP import. or use a separate Scenario for each view with the Local GAAP data being fed into each scenario. One of the main differences between the two views would be pre-acquisition TBs for newly acquired companies being included in the management view for comparative purposes. Would be Interested to hear anyone's feedback or suggestions - thanks!
Invalid Cube Name Error During Data Load
My colleagues in OneStream, have you seen this error before? Since this is the first time I’ve come across it in a standard load scenario with everything else validating, I thought I’d share here to compare notes. Any insights on what could be “behind” this error in practice would be really helpful for building a knowledge base around less common OneStream load errors. While running a data load in OneStream, I encountered an "Invalid Cube Name" error. What made this surprising is that all the usual suspects checked out fine: Workflow setup was validated. Data sources were reviewed. Transformation rules were checked. Rules on members who call cubes were also confirmed. Cube mappings looked correct. Despite all of these checks, the error still occurred. This message is unusual because it doesn’t typically appear if the metadata, cube structure, or mappings are aligned. In most cases, it points to something deeper in how OneStream is resolving the cube context for the workflow profile or the entity being processed. Have you seen this error before on OneStream? ( Invalid Cube Name Error During Data Load) Cheers
DM Step Issue with Exporting Data with View Filters
Hi team, I'm trying to export data using a Data Management step with view filters. When I specify the view as V#Periodic,V#YTD, only V#Periodic data records is being extracted. If I reverse the order to V#YTD,V#Periodic, then only V#YTD data records get extracted. Has anyone faced this issue or knows how to correctly extract data with View dimension filters? Thanks in advance! 🙂How 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.BI Blend Table - What is the significance of sEntity?
I just created a BI Blend table and when I open the file using a data adapter, I see the data unit and aggregation fields all have an extract column prefixed with "s" (i.e., sEntity, sScenario, sAccount, sUD1, etc.). What do these columns represent?
