1

The documentation is almost useless most of the time and it's infuriating when you have a specific problem.


When doing migrations it would be extremely useful to quickly find out what sequence (or lineage) each entity needs in order to be populated/migrated.


An example is Products -> Released Products - but you can't (or shouldn't) just import released products into a new system unless you have already populated the Dimension Groups and Reservation Hierarchy etc, so there is an easy to work out sequencing there, but so many other areas are really awful to have to work out.


I have particularly struggled with Users, Workers, People and Mobile Device Users.... as they use system id's it's difficult to map all these between your various environments, and to work out which order to Import the multiple related entities.


The mobile device menus is another one - there are about 8 different entities that have to be done in a very specific order... why can't you simply have sections in the documentation that show this? or packages/templates that are easy to find...


Thanks

Phil

STATUS DETAILS
New