• Replies 15 replies
  • Subscribers 343 subscribers
  • Views 44 views
  • Users 0 members are here
Related

Ticket History from v11 to v12

Ray Bernard
$organization

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

Parents
  • $organization

    This is a very old thread but as we've just moved from v10 to v11 to v12.5 in less than a year this is now a problem for us. We have several Extractions built on lists that no longer exists. I have some understanding creating other columns from the old ticket history to reflect in the new screens. I have no idea how this is done. What did some people do? Is there any way we can get the details to our IT Director so we can do the same. I don't understand why they would implement something that eliminates years of ticket history and not prepare people sooner. Of course, I want access to this legacy information through all upgrades. 

    Any help and guidance would be appreciated. 

    Thanks.

Reply
  • $organization

    This is a very old thread but as we've just moved from v10 to v11 to v12.5 in less than a year this is now a problem for us. We have several Extractions built on lists that no longer exists. I have some understanding creating other columns from the old ticket history to reflect in the new screens. I have no idea how this is done. What did some people do? Is there any way we can get the details to our IT Director so we can do the same. I don't understand why they would implement something that eliminates years of ticket history and not prepare people sooner. Of course, I want access to this legacy information through all upgrades. 

    Any help and guidance would be appreciated. 

    Thanks.

Children
  • $organization in reply to Adria Gunter

    Unknown said:

    [...] Of course, I want access to this legacy information through all upgrades. 

    The network has recently been recommending a move to "standard" ticketing and package history tables, however this is not required. I made a group of custom SSRS tabs for this purpose, and until/unless the underlying standard history tables are modified to support one or more custom columns, we will continue to use these.

    Don't let anyone tell you you have to abandon any of your data!

    Re: "eliminates years of ticket history", it's quite possible that your old ticketing/package history tables are still present, but not currently displayed in the client. In this case existing list/extraction elements may still work, or could be easily re-created. (Having access to your database via SSMS will be extremely helpful in re: this issue, as it always is.)