Dynamic members are recognized during automated data loads?

Summary:

We enabled a parent member to allow dynamic children in FreeForm Planning. The dimension build completes successfully via Data Management, and the new dynamic member is visible and retrievable in Smart View—no database restructure required.

We can manually lock and send data to the member via Smart View, and data loads successfully when done manually. However, when running the data load integration, it fails with a “member not found” error.

It appears the Data Integration export to Essbase isn’t recognizing the new dynamic member, even though it was created successfully during the dimension build.

Has anyone encountered this issue or found a workaround to ensure dynamic members are recognized during automated data loads?