Validation Error: No security access to data cell being cleared
Hi Team, We have a client that upload excel templates using xfdrange into OneStream. They have different files per Business Unit (UD2). Two of the files run into the following intersection error during the validation step: All the other files are correct, however, when they upload these two files, all data intersections (from all other files) are suddenly also invalid intersections. For examples, the line listed here is not from either of the two files but from a seperate file that has no errors when uploaded individually). When you would navigate to "Intersection" instead of "invalid Intersection (1)" all data intersections from all files are there. Only the local users get this validation intersection, when I (administrator) would run "Validate" from this screenshot, the error dissapears. Strange thing is: they have uploaded data on this intersection before in previous Forecast Scenarios without errors Security has not changed for either the application, user, workflow profile, entity etc. these two files both have an account that is only used there but is set up in the same way as all the other accounts (and previously could be loaded in other scenarios). Could just be a coincidence. Application Security: ModifyData is set to Everyone One thing to note is that this is a new forecast scenario we recently created for them, however, setup is the same way as the other forecast scenarios in terms of security. I am also having a hard time understanding the error and why it is refering to "clearing data" in the validate step. Anyone that can help me a little bit more in understanding the error or knows what could cause this? Thanks in advance!
Validation Errors mapping to placeholder
Hey Folks, I am looking to map all validation errors that might occur during an automated load to a placeholder member in the UD1 dimension, but i am running into issues as the mask rule approach is not working. Does anyone else have any other way to make this work? Below is what i have tried but i still get kickouts in the validation step of the load process.
Processing Blank Columns | Direct Import/Load v Standard Import
Rolling Quarterly Forecasts - to Import 12-month flat files - Several times daily during a cycle - 12-month Matrix Data Source 1. Forecast Q1 '25 flat file - Columns Q1-Q4 '25 = amounts 2. Forecast Q2 '25 flat file a. Columns Q1 '25 = blanks b. Columns Q2-Q4 '25 = amounts c. Q1 '25 to be refilled with actuals - using a DM Job after the initial Import 3. Forecast Q2 '25 flat file - Columns Q1 '25 = blanks a. Direct Import/Load - Wiped out refilled actuals in Q1 '25 = blanks b. Standard Import (Import, Validate, Load) - Kept refilled actuals in Q1 '25 4. Blank Columns - Q1 '25, etc = Prior Periods a. Why do Direct and Standard process blank columns differently? b. How to make Direct process blank columns like Standard? - Keep actuals in Q1 '25/prior periods in OS Data Cubes TY.
Data import from Stage to Cube
Hi, We successfully imported data from stage to cube. But while creating cube views, I am getting fewer records. Not all data is showing up in cube view. I checked the tables in the database; they have all the lines, but the cube view is importing only the first line. What can I do to get all the lines calculated in Cubeview? This account has 1343 records but cubeView fetches only 1st line.
