Infomaker header not displaying after update

Hi Kim

Long shot – does an Infomaker object by that name exist in more than one of your referenced pbl’s? If it’s ahead of the new one in the list, Tess will run that one instead.

________________________________
Ken McSwain

Systems and Technology Manager

Australian Chamber Orchestra

ken.mcswain@aco.com.au

Ph   +61 2 8274 3833 ::  Mob +61 418 659 360 :: Fax  +61 2 8274 3801

PO Box R21, Royal Exchange NSW 1225

2 East Circular Quay, Sydney NSW 2000

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kim Lee
Sent: Monday, 10 September 2012 15:24
To: Ken McSwain
Subject: [Tessitura Technical Forum] Infomaker header not displaying after update

Hi,

I am having trouble with getting an updated Infomaker header to appear in the Tessitura client, and was hoping there is a guru out there who can spot where I have gone wrong.

Here is the scenario:  we have decided to use the street3 field in v11, and we want this data to display on our custom Infomaker header. So we've edited our local sproc to include this feild in the output. As we were updating the sproc, we've removed the full_name2 field also. Impusers have been given Execute rights on the sproc.

I've then edited the Infomaker object, repointing it to the updated sproc. I've updated the column specifications to ensure they match in order and data type to the sproc output. I then edited the design to include the street3 field. When I preview within Infomaker, there are no errors and all the data is there.

We've got v11 in one of our test environments. The Infomaker object I'm editing has been migrated in version 12.1, and it exists in one of the libraries specified in T_DEFAULTS.local_libraray_list

When I log in as the User Group who has this particular header assigned in Security, instead of seeing our custom header I get the generic Infomaker header. I have run a profiler trace while accessing a constituent record logged in as the User Group with this header assigned, and I can see that its retrieving the correct Infomaker object from T_FORMAT_INFO, but for some reason its AP_DONOR_HEADER1 that’s being executed instead of our local procedure attached to our Infomaker object.

Any suggestions on what might be going wrong?

Thanks in advance!

Kim

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 Kim

Long shot – does an Infomaker object by that name exist in more than one of your referenced pbl’s? If it’s ahead of the new one in the list, Tess will run that one instead.

________________________________
Ken McSwain

Systems and Technology Manager

Australian Chamber Orchestra

ken.mcswain@aco.com.au

Ph   +61 2 8274 3833 ::  Mob +61 418 659 360 :: Fax  +61 2 8274 3801

PO Box R21, Royal Exchange NSW 1225

2 East Circular Quay, Sydney NSW 2000

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kim Lee
Sent: Monday, 10 September 2012 15:24
To: Ken McSwain
Subject: [Tessitura Technical Forum] Infomaker header not displaying after update

Hi,

I am having trouble with getting an updated Infomaker header to appear in the Tessitura client, and was hoping there is a guru out there who can spot where I have gone wrong.

Here is the scenario:  we have decided to use the street3 field in v11, and we want this data to display on our custom Infomaker header. So we've edited our local sproc to include this feild in the output. As we were updating the sproc, we've removed the full_name2 field also. Impusers have been given Execute rights on the sproc.

I've then edited the Infomaker object, repointing it to the updated sproc. I've updated the column specifications to ensure they match in order and data type to the sproc output. I then edited the design to include the street3 field. When I preview within Infomaker, there are no errors and all the data is there.

We've got v11 in one of our test environments. The Infomaker object I'm editing has been migrated in version 12.1, and it exists in one of the libraries specified in T_DEFAULTS.local_libraray_list

When I log in as the User Group who has this particular header assigned in Security, instead of seeing our custom header I get the generic Infomaker header. I have run a profiler trace while accessing a constituent record logged in as the User Group with this header assigned, and I can see that its retrieving the correct Infomaker object from T_FORMAT_INFO, but for some reason its AP_DONOR_HEADER1 that’s being executed instead of our local procedure attached to our Infomaker object.

Any suggestions on what might be going wrong?

Thanks in advance!

Kim

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!