XFGETCELL(), XFSETCELL() PERFORMANCE
Hi all, Every forecast cycle we get the same performance complaints from the same region group of users. They are always uploading massive amounts of data and refreshing massive amounts of data in the same workbooks using the XF functionality in Excel. To be clear, we have tried multiple times to convince them that they should be importing that data via CSV and advising that they will not get the same performance using the XF functions. We have also tried having OneStream re-index the databases before these cycles and we have regular daily app pool recycles. The OneStream data logs really don't show any significant refresh issues (less than 5 minutes usually) but the one user doing all this work is insisting that it's taking hours and hours to finish refreshing and they often have to close and reopen Excel and re-launch OneStream. We have raised multiple tickets and OneStream does not see any back end issues. We have looked at their Excel preferences and tried different options there but no improvement. I am 100% out of ideas so if anyone out there has any thoughts, would love to hear what you've done to resolve these issues. I'm going to post this as well somewhere in the community where Excel discussions happen. Thanks for any advice.
Cubeview Drill Down issue: Load Results for Importe Cells is empty
Hello there, We are having an issue when using the Drill Down option from a Cubeview, and it's that after getting to a base data cell within the Drill Down window, and then trying to navigate to stage using the "Load Results for Imported Cell", the results window is displayed empty: The workflow that is being used it's a simple Import, Validate and Load, that retrieves the imported data from a Connector and there is no further data processing once it's in the Cube. From the Workflow Page we can use Drill Down and Drill Back just fine. Any ideas of why is this happening? Thank you. Oriol
Change Load method through connector code
Hello everyone! Quick question. Does anybody know how to change the Load Method for a ProcessDataTable through the connector code? We have a dashboard where the user wants to choose the Load Method with a radio button. We are able to pass that parameter to the code and change the api.LoadMethod property to Append but the load still executes as Replace. The above works if we change the load method directly in the WF, but not from the code
Matrix Data Load Basics
I have a matrix data load question. I get the concept of how the matrix data load works. I haven't done too many of them, so I want to make sure I'm not missing the basics. The file I have has the year on one of the first lines in column 9. The next row contains the headers with periods in 12 separate columns. Is there an easy way to get the year from the first line (without a lot of code)? Or should I get year based on the POV? Then I am guessing a complex expression in the time columns to build the OS time key? I know I can do all of this in code, but I don't want to skip over any out of the box functionality or best practices. Any good guides on some of the best approaches with the Matrix load? Thanks, ScottWorkflow Profile Hierarchies: Security Model | Application Security Roles v Workflow Security
Please share your practical advice to secure Workflow Profile Hierarchies per the two requirements below. Thank you. A. Workflow Profile Hierarchies: Admin v Builder/Business 0. 'Cube Root Workflow Profiles' | Admin and Business | Top Level Cube_suffix 1. 'Default/Child Workflow Profile Types' | Admin/Business 'Cube Root Workflow Profiles' 2. Admin 'Parent/Child Workflow Profile Types' | Admin/Business 'Cube Root Workflow Profiles' 3. Business 'Parent/Child Workflow Profile Types' | Business 'Cube Root Workflow Profiles B. Two Workflow Requirements: Admin v Builder/Business 1. Builder not allowed to see/create/edit: - Admin 'Cube Root Workflow Profiles' - 'Default/Child' and Admin 'Parent/Child Workflow Profile Types' | Admin 'Cube Root Workflow Profiles' - 'Default/Child Workflow Profile Types' | Business 'Cube Root Workflow Profiles' - Admin 'Parent/Child Workflow Profile Types' | Business 'Cube Root Workflow Profiles' 2. Admin/Builder allowed to see/create/edit: - Business 'Cube Root Workflow Profiles' -- Business 'Parent Workflow Profile Types': Review, Base Input, Parent Input -- Business 'Child Workflow Profile Types': Import, Forms, Journals C. Security Model: Application Security Roles + Workflow Security | Admin v Builder/Business 0. Security Groups: 'Admin Roles and Builder Roles' and Child Groups = 'Admin Roles' + 'Builder Roles' 1. Application Security Roles | Manage Workflow Profiles = 'Admin Roles and Builder Roles' 2. Workflow Security = 'Admin Roles' = Admin/Business 'Default Workflow Profile Types' 3.1. Workflow Security = 'Admin Roles' = Admin 'Cube Root Workflow Profiles' 3.2. Workflow Security = 'Admin Roles' = Admin 'Parent Workflow Profile Types' 4.1. Workflow Security = 'Builder Roles' = Business 'Cube Root Workflow Profiles' 4.2 Workflow Security = 'Builder Roles' = Business 'Parent Workflow Profile Types' D. Security Model Results: Admin v Builder/Business - 1 + 2 + 3 + 4 = Workflow Requirement 1 = Fail - 1 + 2 + 3 + 4 = Workflow Requirement 2 = Succeed Thank you, SMEs.
