- Thu Jan 24, 2019 12:00 am
#822523
I'm looking to migrate a substantial amount of historical data into a new process in PM so users only have one source to work with. In order to use PM as a future production system, we will need a method to migrate existing data for cases into the tool and ensure each case is at the appropriate state and assigned to the appropriate task.
It seems straight forward to collect the old system information, and walk though the various values, creating the APP_DATA array, and a simple insert into the database. (straight forward because I have not tried yet ).
So, has anyone tried this yet?
If so what have been your difficulties?
The first hurdle I see - -Does the assignment of a new APP_UID have a specific method? I see that the system pretty much depends on APP_UID and APP_NUMBER to be unique values, but neither is defined as unique in the table definition.
It seems straight forward to collect the old system information, and walk though the various values, creating the APP_DATA array, and a simple insert into the database. (straight forward because I have not tried yet ).
So, has anyone tried this yet?
If so what have been your difficulties?
The first hurdle I see - -Does the assignment of a new APP_UID have a specific method? I see that the system pretty much depends on APP_UID and APP_NUMBER to be unique values, but neither is defined as unique in the table definition.