TNEW Adjustments After Initial Event Creation

So brand new build

Production Season Level>Content

I have an event that I place our COVID policy in under TN_Express_Prod_Short_Desc
I have an event image that place under TN_Express_Prod_Img


Go to TNEW and this content carries over automatically in TNEW: Production Season Description and TNEW: Production Season Image URL for Listing respectively when the event is FIRST rendered in TNEW.

A few months go by and then our COVID policy adjusts slightly and the tour sends over new AdMat. Make the adjustments in Tessitura (update language/change out images), but this does not carry over into TNEW.  Is this correct? So we have to update the policy and the images both in Tessitura and TNEW event by event and creating a little extra work?

Hope I'm making sense with this ask. Does anyone have a work around?

Parents
  • Unless you are somehow still using TNEW v6, you generally shouldn't be populating TNEW content from Tessitura.  TNEW v7 does have some kind of legacy system that will pull values from there, but it is inconsistent.  Instead, go to the TNEW admin and set the values there.

    We've definitely had similar issues as we have a customization that needs some of these old content fields populated, and that sometimes conflicts with our settings in TNEW: inconsistently, of course.

    I'd you're trying to save work by changing content at higher production element levels (i.e Title), that limitation irked me initially, but in the end using performance types/performance product types is actually usually a better way to organize things.

Reply
  • Unless you are somehow still using TNEW v6, you generally shouldn't be populating TNEW content from Tessitura.  TNEW v7 does have some kind of legacy system that will pull values from there, but it is inconsistent.  Instead, go to the TNEW admin and set the values there.

    We've definitely had similar issues as we have a customization that needs some of these old content fields populated, and that sometimes conflicts with our settings in TNEW: inconsistently, of course.

    I'd you're trying to save work by changing content at higher production element levels (i.e Title), that limitation irked me initially, but in the end using performance types/performance product types is actually usually a better way to organize things.

Children