Which property, when set to False on a Historical Load Workflow Profile, causes an error during the Import process?

Which property, when set to False on a Historical Load Workflow Profile, causes an error during the Import process?

• A. Is Optional Data Load
• B. Can Load Unrelated Entities
• C. Flow Type No Data Zero View Override
• D. Force Balance Accounts to YTD View

Answer: (B)

In a Historical Load workflow, a key setting controls whether data for entities that aren’t connected by a defined relationship can be loaded. Setting this option to False means the import will not accept data for unrelated entities, and OneStream will raise an error if the incoming data includes such entities. So the issue during Import stems from not allowing unrelated entities to be loaded. Allowing this capability (i.e., setting it to True) lets the import proceed with data for entities that aren’t linked, avoiding that specific error. The other properties control different aspects of loading and viewing data and aren’t about permitting or forbidding unrelated entities, so they don’t cause this particular error.

In a Historical Load workflow, a key setting controls whether data for entities that aren’t connected by a defined relationship can be loaded. Setting this option to False means the import will not accept data for unrelated entities, and OneStream will raise an error if the incoming data includes such entities. So the issue during Import stems from not allowing unrelated entities to be loaded. Allowing this capability (i.e., setting it to True) lets the import proceed with data for entities that aren’t linked, avoiding that specific error.

The other properties control different aspects of loading and viewing data and aren’t about permitting or forbidding unrelated entities, so they don’t cause this particular error.