Create dynamic members using api.ReadDynamicDimensionInfo
Hi, I'm trying to create dynamic members within a dimension using api.ReadDynamicDimensionInfo. I created a custom table within application database. When the service runs, it creates members under the root member even when I pass the "Parent" member's name. Also, the aggregation weight is being set to 0 even when I've passed numerical values. Table: Dimension Library: I want the members to be created under "All_Customers" Code: It works when I use - CreateAndAddrelationships but not with the api mentioned above. Am I doing something incorrect?
Exporting Grid View Filter Results
Hi OneStream Community, I had a question regarding extracting dimension metadata and properties from OneStream. Currently, when we go to the Dimension Library, apply member filters in the grid view, and then right-click and export to CSV, we can download file containing the metadata along with its properties. I’m trying to find out if there is a way to automate this instead of doing it manually. Ideally, I would like to extract the same information (based on member filters or a specific hierarchy) through something like a Dashboard, Data Management step, or Business Rule, so the export can be automated. Has anyone implemented something similar or know of an approach to achieve this?Metadata builder and extensibility
Hi everyone, I am currently using the metadata builder in excel to maintain and keep updated the hierarchies of all dimensions, but I'm having an issue in loading two separate dimensions for UD5. I was planning to build the U5 dimensions as follows: within each dimension, I would have the same base members organized in different hierarchical structures (aka same base members but different nodes between Finance and HR). In Excel, I divided the two dimensions in two separate sheets, because I can reference one dimension at a time in each sheet when I load the XML of the first dimension, I have no issues and the dimension loads as expected. If I make a change to the configuration of that same dimension and load the new xml, I still get no issues. The problem arises when I try to load the XML of the second dimension. The error I get is the following: Error processing XML file type 'Metadata'. Error processing XML. The specified member does not belong to the encompassing dimension. 169989, Cost Centers HR. XML line 127, position 7, element member. The 169989 member is the first base member in the HR dimension. It seems the system refuses to load members that already exist in the Finance dimension. My questions are the following: Is there a problem in the way I designed the UD5 dimensions in excel? OR is it normal that the same base dimension can be loaded for one dimension only, and the second XML (for the HR dimension) should only include the new relationships between the already existing base members and the new nodes of the HR dimension? Thank you in advance for any help, feel free to ask additional info if needed
parent child relationships limited to one hierarchy
This is a problem I run into off and on that's always been annoying but easy enough to work around... until now. When working in a QuickView, for example, I click on the Up Arrow (for Parents) and I get all parents, not just the parent in the hierarchy I'm actually working with. In the most literal interpretation, I can see why this happens. In principle, I think I ought to be able to control this behavior either by the Parent filter or through the addition of a field that lets me choose my current hierarchy. But, in a QuickView, I'm working with one member at a time so it's not the end of the world to just remove the irrelevant parents and maybe do a little manual editing of the member filter if it gets too messy and I really want to keep the QV for future use. The problem comes when using the Grid View set to Display Parent Child Relationships with a member filter to display the descendants within a key hierarchy. I get every parent child relationship for every hierarchy. There's no good way to filter them. They are too numerous to filter by hand. It's just a useless soup sandwich of a dataset. Am I missing something obvious? Am I missing something not-at-all obvious? Perhaps I'm using a completely stupid approach and there's another way to get a nice, concise list of parent/child relationships for a hierarchy.
Export Invalid intersections including validation messages
Hi, I'm aware that from the Validate workflow step, the full list of invalid intersections can be exported as in the picture below (right click > Export): The Validation messages are not included in the export. Is there a way to export the full list of validation messages together with the invalid intersections? Thank you
