Changing Data in Attributes to Order History

After two months I am slowly finding my way through Tessitura and was given the task of updating imported data from a couple of years ago.  When the data was imported from a non-Tessitura software (Millennium, I think), the ticket order history was imported as an Attribute.  The goal is to move the info in Attributes to Orders so we can track which performances guests had purchased tickets for.  Is there a way to change the data in Attributes so it appears as data under Order history?  Is this doable? I've read the documentation on the Import Process Summary, but am hoping someone might have an easier way of explaining what it is I need to accomplish this task.  Suggestions appreciated!  Thanks!

Parents
  • Former Member
    Former Member $organization

    Hi Janelle,

    I think there are two basic approaches you could take here.  The first, and by far more complicated, is to extract the attribute data from Tessitura and then import it back in as order data using the import utility.  There would be a lot of setup involved (creating all of the relevant facilities, seasons, performances, pricing information, etc).  This would give you a true conversion of the data.

    The second option is a little less complex but has some limitations.  You could add the order data directly to the ticket history table.  This would allow you to get at the data with things like output sets and lists and possibly custom reports.  However, you would not have the data in T-Stats or most standard reports.

    Which way you go really depends on how you expect to use the data going forward. If you are hoping to do complex reporting on these purchases I would suggest making the effort to get them set up as actual orders.  If you don't anticipate a lot of reporting requirements, it would be a shorter process to just throw them into ticket history.  Either way, you will need to work with your DBA to get the data formatted correctly and you will want to test the process thoroughly in your Test environment.

    Hope that helps!

    - Levi

Reply
  • Former Member
    Former Member $organization

    Hi Janelle,

    I think there are two basic approaches you could take here.  The first, and by far more complicated, is to extract the attribute data from Tessitura and then import it back in as order data using the import utility.  There would be a lot of setup involved (creating all of the relevant facilities, seasons, performances, pricing information, etc).  This would give you a true conversion of the data.

    The second option is a little less complex but has some limitations.  You could add the order data directly to the ticket history table.  This would allow you to get at the data with things like output sets and lists and possibly custom reports.  However, you would not have the data in T-Stats or most standard reports.

    Which way you go really depends on how you expect to use the data going forward. If you are hoping to do complex reporting on these purchases I would suggest making the effort to get them set up as actual orders.  If you don't anticipate a lot of reporting requirements, it would be a shorter process to just throw them into ticket history.  Either way, you will need to work with your DBA to get the data formatted correctly and you will want to test the process thoroughly in your Test environment.

    Hope that helps!

    - Levi

Children
No Data