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)

The key idea is how the historical load process treats entity relationships during import. The setting Can Load Unrelated Entities determines whether data rows that reference entities not related to the target in the load profile are allowed. When this property is False, the importer expects every data row to reference related entities; if a row points to an unrelated entity, the Import step fails with an error. That’s why this option being false causes an error during Import. Other properties control different behaviors (whether data is optional, how zero data is handled, or forcing a specific view for balance accounts) and do not inherently trigger an import error simply by being disabled. Ensure your source data only includes entities that are related to the target when this setting is False.

The key idea is how the historical load process treats entity relationships during import. The setting Can Load Unrelated Entities determines whether data rows that reference entities not related to the target in the load profile are allowed. When this property is False, the importer expects every data row to reference related entities; if a row points to an unrelated entity, the Import step fails with an error. That’s why this option being false causes an error during Import. Other properties control different behaviors (whether data is optional, how zero data is handled, or forcing a specific view for balance accounts) and do not inherently trigger an import error simply by being disabled. Ensure your source data only includes entities that are related to the target when this setting is False.