| Re: OTM data loading sequence Loading data in to OTM via CSV is very straightforward and should work for the vast majority of data that you would ever wish to load during an implementation.
The "easiest" way to do this is to first key in one record of the data you are trying to load and to then export that data into CSV format. That will give you the template for the CSV data you are trying to load. That unload of data can be done from within the application.
In terms of sequence of loading there are no really fixed rules. For example, you can easily load equipment group data before locations - it all depends on the data you are trying to load and the relationship between the database tables that are impacted. of course, you cannot load a location which references a corporation that has not already been defined, but in general, it should be quite apparent the order you need to load the data in.
I have loaded service provider data via CSV with no issues whatsoever. Again, the "trick" is to load one record via the UI and then export the relevant database tables in to CSV format to make sure you have what you need. |