Which property should a Consultant use to enable a Central Input Import Workflow Profile to import data for multiple entities through one Workflow?

Which property should a Consultant use to enable a Central Input Import Workflow Profile to import data for multiple entities through one Workflow?

• A. Is Optional Data Load
• B. Limit to Defaults
• C. Insert Type
• D. Can Load Unrelated Entities

Answer: (D)

The key idea is enabling a single import workflow to push data into more than one entity. The property Can Load Unrelated Entities allows a Central Input Import Workflow Profile to process and load data for multiple entities in one run, even if those entities aren’t in a parent–child relationship. This is exactly what you need when you want a single workflow to handle data for several distinct entities at once, streamlining the process and reducing separate runs for each entity. The other options don’t provide that capability. Is Optional Data Load would merely allow certain fields to be optional during the load, not extend the workflow to multiple entities. Limit to Defaults would constrain data to default values and mappings, not enable cross-entity imports. Insert Type governs how records are created or updated, which affects data operations but not the ability to load into multiple entities in one workflow.

The key idea is enabling a single import workflow to push data into more than one entity. The property Can Load Unrelated Entities allows a Central Input Import Workflow Profile to process and load data for multiple entities in one run, even if those entities aren’t in a parent–child relationship. This is exactly what you need when you want a single workflow to handle data for several distinct entities at once, streamlining the process and reducing separate runs for each entity.

The other options don’t provide that capability. Is Optional Data Load would merely allow certain fields to be optional during the load, not extend the workflow to multiple entities. Limit to Defaults would constrain data to default values and mappings, not enable cross-entity imports. Insert Type governs how records are created or updated, which affects data operations but not the ability to load into multiple entities in one workflow.