Does Native Integration Support Custom Properties Mapping in Fusion Service (26A)?
Hi community,
I’m referring to the Oracle Fusion Service 26A readiness document:
The document mentions that the integration works “without creating custom properties, or building field maps.”
This makes sense for standard, out-of-the-box fields. However, I’m looking for clarification on the following:
- If we have custom properties (DFF/EFF/custom attributes), does the native integration support them in any way?
- Is there any capability to map custom properties within the native integration setup?
- Or is the expectation that only standard fields are supported, and for any custom field handling we must use an external integration layer?
Specifically, I’d like to understand:
0