Hi,
At the Science Museum, we have legacy ticket data from our previous software, in v11 (and previous versions) in Ticket History. In testing the migration to v12 this valuable information is not longer readily available. While we like the greater detail in the v12 History, we don't want to lose ready access to legacy data. Have any other organizations encountered this? How are you handling it? Are there any alternatives for scripted "back filling"of this data into v12constituent records post migration?
Thanks.
Ray
Unknown said: At the Science Museum, we have legacy ticket data from our previous software, in v11 (and previous versions) in Ticket History. In testing the migration to v12 this valuable information is not longer readily available.[...]
At the Science Museum, we have legacy ticket data from our previous software, in v11 (and previous versions) in Ticket History. In testing the migration to v12 this valuable information is not longer readily available.[...]
We have plenty of legacy data, too, have used heavily customized Ticket History tables table here from day 1 on Tessitura, and in addition have plenty of custom List/Extraction elements to query them. Adding initiator/recipient data to our tables sounds easier to me than trying to cram the square peg of our data into the round hole of the new standard tables, but we'll see (we are only on v12 in Test.)