Hello Community Members,

I’m currently working on exporting a 3DXML for a Physical Product from one system and importing it into another, and I’ve run into a maturity state mapping issue.

In the source system, a custom policy has been implemented where the maturity states are defined differently (for example: A state, B state, C state). However, the target system uses the out-of-the-box (OOTB) policy with standard states such as PRIVATE, IN_WORK, and RELEASED.

The challenge arises during import: when a 3DXML file that is in “C state” in the source system is imported into the target system, it defaults to the IN_WORK state instead of the expected RELEASED state. My objective is to correctly map the maturity states during the import process as follows:

• A state → PRIVATE
• B state → IN_WORK
• C state → RELEASED

I explored using Business Logic (BL) for this mapping, but it did not behave as expected in this scenario. It seems like the state transformation is either not being triggered correctly or is overridden during import.

Has anyone encountered a similar use case or successfully implemented maturity state mapping between custom and OOTB policies during 3DXML import? Any guidance, best practices, or insights into handling this would be greatly appreciated.