If the DFF Attribute Mapper extension is failing during extraction, what is a possible cause?

If the DFF Attribute Mapper extension is failing during extraction, what is a possible cause?

• A. The DFF Attribute Mapper configuration is deprecated.
• B. The target schema uses a non-BI-enabled data type.
• C. You selected an attribute that isn't BI-enabled.
• D. The source Fusion Application was not connected.

Answer: (C)

BI-enabled attributes are the ones the DFF Attribute Mapper can extract. The extension is designed to map fields that are flagged as BI-enabled so they can be processed by the BI extraction pipeline. If you select an attribute that isn’t BI-enabled, there’s nothing for the mapper to output for that field, causing the extraction to fail. That direct mismatch between what the mapper can handle and what’s chosen for mapping is the most likely cause in this scenario. Other options describe issues that would present differently. A deprecated configuration would typically show warnings or require an adjustment in setup rather than fail a specific attribute extraction. A non-BI-enabled data type on the target would indicate a datatype compatibility problem rather than a mapping issue with an attribute. And if the source Fusion Application wasn’t connected, you’d expect a connectivity error prior to any attribute-level mapping.

BI-enabled attributes are the ones the DFF Attribute Mapper can extract. The extension is designed to map fields that are flagged as BI-enabled so they can be processed by the BI extraction pipeline. If you select an attribute that isn’t BI-enabled, there’s nothing for the mapper to output for that field, causing the extraction to fail. That direct mismatch between what the mapper can handle and what’s chosen for mapping is the most likely cause in this scenario.

Other options describe issues that would present differently. A deprecated configuration would typically show warnings or require an adjustment in setup rather than fail a specific attribute extraction. A non-BI-enabled data type on the target would indicate a datatype compatibility problem rather than a mapping issue with an attribute. And if the source Fusion Application wasn’t connected, you’d expect a connectivity error prior to any attribute-level mapping.