File Explorer Incoming workflow folders missing in copied applications
This post is to provide information about File Explorer Incoming workflow folders. Based on what we've seen in our environments, when an application is copied, the new application does not contain the folder structure located at: \File Share\Applications\<Application Name>\Incoming\<Cube Root Name>_Cube\<Workflow Base Input Name>\<Workflow Import Name> We noticed these folders were missing in our last application copy when we were trying to copy files through SIC and drop them into the workflow import folders since our requirement was to drop them there for users to manually import when they choose (instead of automatically loading the files through batch import from batch harvest). To fix this issue we exported the Workflows and re-imported them back into the copied application. This triggered OneStream to create the cube root folders and workflow folders for the workflows that were imported. Hope this helps someone else who might be running into the same issue.
Need to send data from OneStream to Snowflake using an existing SIC ODBC connection
Hello, What is the best way to send data from OneStream to Snowflake using an existing SIC ODBC connection? Currently I am using SIC ODBC connection to query data from Snowflake and now I would like to send data back to Snowflake.
loading sub-ledger data into OneStream
Hi Community :) We are currently in development with regard to loading sub-ledger data into OneStream, but the balance specifications are so granular that we currently have them split into about 10 distinct loads. Because of this setup, our end users are being forced to manually click "Load and Transform" 10+ times to get a complete sub-ledger balance loaded for the period. Obviously, this is tedious, creates a poor user experience, and introduces a lot of room for human error. We want to streamline this. What is best practice to do this?
How to "Import" "in parallel" via a "OneStream Connector" to a "Data Warehouse"?
Please share your practical advice to help us meet the new Integration requirements. - I couldn't find a OneStream KB/post nor a good result from free Gemini. - We're using SAAS on v9.0 to move to v10 upon its upcoming release. Thank you folks for sharing your expertise.Import with Vertical Extensibility or Extensible Dimensions
Hi, I can’t get my data import to work with vertical extensibility, and I’d like to understand how this situation is supposed to be handled. In short, the import validation fails on accounts that are extended for an entity. The entity belongs to a cube that is vertically extended from the primary workflow cube. Detailed situation I have extended dimensions and two cubes that use those dimensions. CubeParent contains a parent entity with dimensions applied. The parent entity resides in the parent entity dimension. CubeChild has dimensions that are extended from the parent’s dimensions. The child entity resides in the child entity dimension. As a result, each cube has its own unique entity dimension containing its respective entity. Additional configuration details: CubeChild has Is Top Level Cube For Workflow set to False. CubeParent is the top-level cube and has the Workflow Profile created from it. The child entity has been added as a child of the parent entity in the parent’s entity dimension (see screenshot). CubeParent has the Cube References tab configured correctly. Data import issue I have configured a data source that reads from a CSV file. The data source successfully loads the CSV into the staging area. However, the transformation step fails. The failure occurs only for the child entity’s extended account, not accounts in the ParentCube account dimension. The transformation rules when created are associated with a cube. If the cube is not that of the workflow profile the transformation rule does not appear in the import configuration step. Question How should data be imported for an entity that exists in a workflow that has different dimensional detail than the cube it belongs to because it is using vertical extensibility?
