Is there a document somewhere talking about how the new price layer table structures work? I see the names in the table structures document, but no real discussion of how they replace the old T_PMAP and T_SUBPRICE. I've got a number of customizations I need to update for V12, so any such information would be very helpful. I'm slowly sussing it out, but worried I'll miss something. For instance, I expect I'll need to conditionally account for rows in T_PRICE_EVENT?
Gawain,
I don't know of a document that lays this out. But you might try opening up VB_PMAP to see how they constructed the old data model out of the new one. I spent a little time reviewing it before I started my updates to make our custom reports compatible and it was instructive.
- Levi
There is a document for this, and a Tessitura Hosted Training recording. Both highly recommended if you are going to be making changes for V12.
The Document: http://www.tessituranetwork.com/network/Learning/Documentation/v12/Preparing%20Customizations%20for%20v12.aspx
The THT: http://www.tessituranetwork.com/network/Learning/Tessitura%20Hosted%20Training%20for%20v12/Customizations%20and%20Version%2012.aspx
David
Thanks David! I guess I'd scanned over those, but somehow assumed the wouldn't get into the nitty-gritty. I'm going through them now.
Thanks Levi,
Somehow missed that view. I'll dig through that now.
So, I'm not just having to pull data from these tables for our customizations, I also need to add data. We have a custom report that allows our box office to fill in all price types automatically from the base price (as well as doing a number of other things, including connecting those prices to custom tables that allow us to upload our Tessitura financial data to another financial system).
A couple of questions: are all these tables using identity primary key columns, and are there stored procedures or functions that are the preferred way to add data to these tables?
Thanks,
Gawain
Ah, I can see that they are identity columns. Yay! Never liked AP_GET_NEXTID.