Howdy Folks,
We have noticed that when we run an output set the data in phone_1 shows up under the phone_2 column and vice versus, however when you look at the constitutents record the data is where it should be. I went into t_keyword to verify where the data is pulling from but those values are not in that table, where else shall I look to correct this issue?
Naomi
Hi Naomi,
Look in the stored proc AP_GET_PHONES. The SELECT statements there for day_phone, eve_phone and fax_phone reference ID values that are keys into TR_PHONE_TYPE.
Jonathan
Hi Jonathan,
Those values are accurate. The data is accurate it is just when I run the output set it’s backwards. I think it is being temperamental.
Thank you have a good day!
Naomi Williams
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jonathan Smillie Sent: Wednesday, March 24, 2010 3:07 PM To: Naomi Williams Subject: Re: [Tessitura Technical Forum] Switching Phone1 and Phone2 in the output set builder
Look in the stored proc AP_GET_PHONES. The SELECT statements there for day_phone, eve_phone and fax_phone reference ID values that are keys into T_PHONE.
From: Naomi Williams <bounce-naomiwilliams9587@tessituranetwork.com> Sent: 3/24/2010 2:39:19 PM
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!
One more place to check before you just put it down to the full moon - there's a local procedure that's also called from AP_GET_PHONES, predictably called LP_GET_PHONES. If you haven't already, double-check there's nothing in there that's overriding the selection from the base stored procedure.
From: Naomi Williams <bounce-naomiwilliams9587@tessituranetwork.com>Sent: 3/24/2010 3:26:06 PM
Did you check tr_query_element to see if data select got switched somehow?That is where output set builder figures out what to pull into the output.
This one used to boggle my mind too, and I looked at AP_GET_PHONES and at first I thought the right phone types lined up, but after some trial and error with the procedure, I figured out that the default essentially does flip them. It's sort of confusing because that procedure references day vs eve not 1 vs 2, even though the query elements say 1 and 2.
If you want phone1 to be phone type 1 and phone2 to be phone type 2, unless you've already got your own logic in LP_GET_PHONES setting @eve_phone to phone type 2 and @day_phone to phone type 1, what the default does is flipped.