API: ExecuteLocalProcedure table names.....or not

I wonder if Tessitura is defining the "out of the box" table names somewhere in the web service? Since the procedure is returning multiple datatables in the same format that you are getting but maybe they do something in the webservice such as ds.table(0).tablename = "Orders". Not sure since we can see the code in the webservice.

In your code behind, you could always define the name yourself.

Marty Jones

Director of Information Services

Omaha Performing Arts
1200 Douglas Street

Omaha, Nebraska 68102

P 402.661.8469

Marty.Jones@omahaperformingarts.org

www.omahaperformingarts.org

For tickets, call Ticket Omaha at 402.345.0606

From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Nathan Campbell
Sent: Monday, April 04, 2011 5:59 PM
To: Martin A. Jones
Subject: [Tessitura Web Forum] API: ExecuteLocalProcedure table names.....or not

I'm developing a custom procedure to use with ExecuteLocalProcedure (my favorite method!)

For the first time since I've been using this, I'd really like to have the table names defined like all of the 'out of the box' methods (so in my code-behind I can use table["name"].row[ ]  etc....)

Instead - the table names are returned simply as LocalProcedure1, 2, 3, etc.....-

I tried to make SQL output the dataset as XML using FOR XML PATH but that wasn't at all what I wanted.

AOE tried this? It's certainly no big deal and I can handle it either way - but just thought it would be handy

Thanks 

You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web 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!

I wonder if Tessitura is defining the "out of the box" table names somewhere in the web service? Since the procedure is returning multiple datatables in the same format that you are getting but maybe they do something in the webservice such as ds.table(0).tablename = "Orders". Not sure since we can see the code in the webservice.

In your code behind, you could always define the name yourself.

Marty Jones

Director of Information Services

Omaha Performing Arts
1200 Douglas Street

Omaha, Nebraska 68102

P 402.661.8469

Marty.Jones@omahaperformingarts.org

www.omahaperformingarts.org

For tickets, call Ticket Omaha at 402.345.0606

From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Nathan Campbell
Sent: Monday, April 04, 2011 5:59 PM
To: Martin A. Jones
Subject: [Tessitura Web Forum] API: ExecuteLocalProcedure table names.....or not

I'm developing a custom procedure to use with ExecuteLocalProcedure (my favorite method!)

For the first time since I've been using this, I'd really like to have the table names defined like all of the 'out of the box' methods (so in my code-behind I can use table["name"].row[ ]  etc....)

Instead - the table names are returned simply as LocalProcedure1, 2, 3, etc.....-

I tried to make SQL output the dataset as XML using FOR XML PATH but that wasn't at all what I wanted.

AOE tried this? It's certainly no big deal and I can handle it either way - but just thought it would be handy

Thanks 

You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web 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!