Hi Anurag,

Product 360 is very flexible to that point. Usually you have an XML, load it into the Import Perspective of the Desktop UI and start building out your import mapping for that format and you are good. There is no predefined mandatory format you'd have to follow.

Best,

Stefan

Attached is a very simple export template and some data resulting from that export that you should be able to load into any import project.

Anurag,

I have taken a common approach for doing XML exports that makes them very easy to import back into P360. One of the big rules is that identifiers and qualifiers for entities in P360 are XML attributes.

Taking that approach, I can create an export of every data element that will round trip easily back into P360. It's like having an XML backup of your database.

-Dave

I do exactly the same thing as Dave--identifiers and qualifiers are attributes, and fields are sub-entities. I've created an export and import for most of our data model in this fashion.

It would be great if Product 360 had a feature to generate XML like this for any data model dynamically, sort of like how the meta pages for the REST API are automatically generated based on the data model. That would create a transport format that's very easy to set up and use without having to write a lot of custom imports and exports.

Please consider this a feature request, Stefan ; )