Customize - extend data tables - add fields to existing tables?

Hi Larry

Our practice has been to create a local table, called for example, LTR_Facility_Extended, with the same key field/s, as you say. (and to run a nightly/ad hoc update job to add new rows from the main table to the extended table ,with default values, if you need them to stay in step..

Then you can use the GetLocalDataEx or UpdateLocalData , or ExecuteLocalProcedure API methods to work with the data from your website.

I certainly wouldn’t want to make any changes to native Tessitura tables. Even adding a trigger is something I would think about very carefully before doing.

Ken McSwain Business solutions Manager

kmcswain@sydneyoperahouse.com

T+61 2 9250 7876  F+61 2 9251 7821  M 0418 659 360

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

Hi,

What is the best practice for extending an existing table?  Is it possible to add "user-defined" fields to existing tables, (and if so, what are the naming conventions & procedures, etc), or do we need a custom "local table" that has the same key to provide a one-to-one linking between the standard Tessitura table and our local table?  If this is the case, then is there any automation provided by the Web API that will return our custom fields, or must I also build local procedures, call those separately, and join the tables logically in code after retrieving the data from the standard Tessitura web API, and our local procedure API call?

One example would be to provide 3 custom fields for the "TR_Facility" table.  Tessitura wouldn't use this data anywhere, but we will use it on our web site.

Thank you,

Larry

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi Larry

Our practice has been to create a local table, called for example, LTR_Facility_Extended, with the same key field/s, as you say. (and to run a nightly/ad hoc update job to add new rows from the main table to the extended table ,with default values, if you need them to stay in step..

Then you can use the GetLocalDataEx or UpdateLocalData , or ExecuteLocalProcedure API methods to work with the data from your website.

I certainly wouldn’t want to make any changes to native Tessitura tables. Even adding a trigger is something I would think about very carefully before doing.

Ken McSwain Business solutions Manager

kmcswain@sydneyoperahouse.com

T+61 2 9250 7876  F+61 2 9251 7821  M 0418 659 360

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

Hi,

What is the best practice for extending an existing table?  Is it possible to add "user-defined" fields to existing tables, (and if so, what are the naming conventions & procedures, etc), or do we need a custom "local table" that has the same key to provide a one-to-one linking between the standard Tessitura table and our local table?  If this is the case, then is there any automation provided by the Web API that will return our custom fields, or must I also build local procedures, call those separately, and join the tables logically in code after retrieving the data from the standard Tessitura web API, and our local procedure API call?

One example would be to provide 3 custom fields for the "TR_Facility" table.  Tessitura wouldn't use this data anywhere, but we will use it on our web site.

Thank you,

Larry

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!