You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

*Important Awareness* Regarding Planning Data Exports in 26.10

in Planning 2 comments

Summary:

Recently I needed to edit a Planning data export (used to be in Application→Overview→Export Data, now moved to the Import Export tab of the Jobs card … native Planning exports, not via DM/DI) that we have had around for years and years prior to 26.10. After making said edits in 26.10, saving, and running the Data Export job, it appears that a) the generated export file name and b) positions of all dims represented in the POV field are both completely different.

As you can imagine this causes all sorts of downstream trouble with integration layers and other external platforms consuming said files, since these types of platforms are expecting a consistent file name with consistent field definitions. Interestingly, and I imagine it's because the export job definition is fully stored in the underlying .XML in the app file structure, jobs which were created/edited prior to 26.10 are unaffected … well, until they are saved using the revamped 26.10 dialogs. Effectively we would now need to review every single outbound using native planning exports and adjust / compensate for the new expected

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!