Stage data not available in the cube after load

Question

Hi everyone,I’m observing an inconsistent behavior during a standard OneStream Import (Bulk Load) and would like to check if anyone has faced something similar. We just updated to 9.3 Using standard Import (no custom Business Rules)	Workflow is annual	Loading multiple months (e.g., 2026M8 and 2026M9) in a single execution	All dimensions are identical except Time and UD8 If I load the data below, only the -430K value is not loaded into the cube for some reason,-150k and 1mil are fine. However, if I run the same load a second time, the value is loaded correctly. 4 valid rows but only 3 loaded to the cube.If I remove the other two rows and do this, the data is loaded correctly on the first attempt. 2 valid rows and all loaded to the cube.If i do this, delete the S36 for M9, M8 shows correclty as well, at the moment i include M9 with S36 if fail again. In this design, weekly granularity is implemented using a User Defined dimension (UD8), meaning that the same week member (e.g., S36) can validly appear in multiple months (e.g., M8 and M9). A similar issue is observed with S40, which appears in both M9 and M10; when executing a full data load, the S40 intersection for M9 is not populated, while the remaining data loads correctly. The issue occurs only in scenarios where the same week (i.e., the same UD8 member) is used across multiple periods, while all other weeks that are unique to a single month are loaded without any issue.Workflow config: Have you seen that? thanks in advance

GParreiras · Accepted Answer

Looks like the issue was fixed with thePF1-12494 release

ChristopherBriscoe · Answer

This is not anexpected behavior. Without seeing the full application it's difficult to be certain, but:T#2026M8:U8#S36 and T#2026M9:U8#S36 are different cube intersections, so using the same UD8 member across multiple periods should not prevent one record from loading. The fact that all rows validate, the missing record loads correctly on its own, and the same load succeeds on a second attempt suggests a load-processing issue rather than a transformation problem.I would compare the fully transformed Stage intersections (including View, Origin and all UD dimensions), check whether UD8 is being used as a Workflow Channel dimension, and test loading the periods separately. That should help determine whether the issue is related to multi-period loading or Workflow Channel processing. Maybe you should pop in a support ticket on ServiceNow.

Sign up

Login with SSO

Login to the OneStream Community

Login with SSO