• Replies 4 replies
  • Subscribers 246 subscribers
  • Views 122 views
  • Users 0 members are here
Related

TNEW Adjustments After Initial Event Creation

Jeremy Painter (Past Member)
$organization

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?

  • $organization

    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.

  • $organization in reply to Gawain Lavers

    What Gawain said.  I think you maybe able to login to the TNEW v7 admin and Clear Cache that will pull over some of the legacy content fields from the Application  - but at that point you're already logged into TNEW admin and it's much easier to update content from there.

  • $organization

    My usual go to is the TNEW_User_Guide site map and using whatever the content settings are in there.

    To be honest I use TNEW Admin for almost everything (except for Local system table stuff like form fields, delivery methods, dynamic email content etc.)

  • $organization

    Hi! Marley Wynne here, Member Success Manager for TNEW. I thought I'd share some more details about what is happening.

    In v7, which all TNEW sites are using now, most of the Content and Setting management has moved to the TNEW Admin site. There is a concept called "pseudo-migration" that can happen if you are putting content in the Content Tab of the Prod Season or Performance:

    Pseudo-Migrated: Functionality moved to the TNEW Admin; data is synced from Tessitura until edited in the TNEW Admin.

    Jeremy, I think this is why you are experiencing your changes not reflected online. Without knowing more about your business case, my recommendation would be to manage content in the TNEW Admin site. There is a feature called the Property Synchronization that will take the content you add in the TNEW Admin site and write it back down to the Tessitura application, which makes it available to pull via the API if you have a web firm that is trying to pull content like this to display on your front end site. Here is more information:

    https://www.tessituranetwork.com/TNEW_7/TNEW.htm#Topics/Property_Sync.htm

    I hope this helps!

    Best,
    Marley