Has userreports.pbl vanished?

Hi Matt

There have been a few slightly confusing changes to the standard/user reports practice along the way. This is from the upgrade instructions for v9.x:

A new version of SampleFormats90.pbl is included with this release. It contains sample data windows for reports; acknowledgement, renewal, confirmation formats, constituent headers and custom screens.  This library, along with the Standard Reports PBL, replaces the UserReports.PBL of previous releases.  The UserReports.PBL library should be considered deprecated for future use.  These files are not used directly by the Tessitura application but are used for reference and as a starting point for customizing standard processes.

Tessitura standard report formats are now distributed with each upgrade; a new version of TessituraStandardReports90.zip is included with this release. It contains datawindows for the standard reports.

 

For Tess to pick up your new localised datawindow object, it needs to live in a pbl referenced in your t_defaults  table, in the LOCAL_LIBRARY_LIST entry. You can have multiple local libraries in the list, separated by commas.

Our LOCAL_LIBRARY_LIST looks like this:

T:\User Reports\ucss_rpt.pbl, T:\User Reports\ucss_rpt_1.pbl, T:\User Reports\tessimports.pbl, T:\User Reports\ucss_const_rpt.pbl,T:\User Reports\ucss_cust_tab.pbl,T:\User Reports\ucss_t_fmt.pbl, T:\User Reports\ucss_temp.pbl

 

We decided to split each of the different types of local objects into their own pbl, to make it a bit easier to keep control; so the ones referenced in T_FORMAT_INFO are saved  into T:\User Reports\ucss_t_fmt.pbl.

 

So – the quarry for digging up the existing Tess report defs is either  SampleFormats90.pbl or TessituraStandardReports90.pbl (but that’s not where Tess runs them from, that’s just a set of copies for you to play with, really); you need to make  a copy of the one you want to use as a starting point, and rename it (as you did), but then you should save your copy into a new library, and reference that library in your LOCAL_LIBRARY_LIST entry in t_defaults – and of course your Tess client needs to be able to see the folder that you use – using a folder path of  T:\User Reports\ is pretty much the standard way to do that.

 

 

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,

I wanted to have a look at modifying the d_mailing_labels object that Tessi uses in the User Defined Object From a List. From what I understand of the documentation and hunting around on TASK, when you select something like a label, it:

a) Looks up the object in T_FORMAT_INFO.

b) Then (and this is not perfectly clear in the documentation), I presume it goes and finds the D object (say, d_mailing_labels) from userreports.pbl?

Where I'm running into problems is that I can't find a userreports.pbl in our User Reports folder. The only .pbl that contains those label objects in question is one called SampleFormats80.pbl.

I tried a quick test, just by making a copy of d_mailing_labels and calling it ud_mailing_labels and getting the T_FORMAT_INFO to point to it. It didn't work.

So my questions are:

1. Where is the .pbl that the existing label objects are stored in and that any custom label objects need to be stored in?

2. Has it been renamed from userreports.pbl to something else, or have I got something wrong?

And maybe at some stage, it would be great to see some documentation added that explains clearly where labels need to be located to be referenced by T_FORMAT_INFO?

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!

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====

Hi Matt

There have been a few slightly confusing changes to the standard/user reports practice along the way. This is from the upgrade instructions for v9.x:

A new version of SampleFormats90.pbl is included with this release. It contains sample data windows for reports; acknowledgement, renewal, confirmation formats, constituent headers and custom screens.  This library, along with the Standard Reports PBL, replaces the UserReports.PBL of previous releases.  The UserReports.PBL library should be considered deprecated for future use.  These files are not used directly by the Tessitura application but are used for reference and as a starting point for customizing standard processes.

Tessitura standard report formats are now distributed with each upgrade; a new version of TessituraStandardReports90.zip is included with this release. It contains datawindows for the standard reports.

 

For Tess to pick up your new localised datawindow object, it needs to live in a pbl referenced in your t_defaults  table, in the LOCAL_LIBRARY_LIST entry. You can have multiple local libraries in the list, separated by commas.

Our LOCAL_LIBRARY_LIST looks like this:

T:\User Reports\ucss_rpt.pbl, T:\User Reports\ucss_rpt_1.pbl, T:\User Reports\tessimports.pbl, T:\User Reports\ucss_const_rpt.pbl,T:\User Reports\ucss_cust_tab.pbl,T:\User Reports\ucss_t_fmt.pbl, T:\User Reports\ucss_temp.pbl

 

We decided to split each of the different types of local objects into their own pbl, to make it a bit easier to keep control; so the ones referenced in T_FORMAT_INFO are saved  into T:\User Reports\ucss_t_fmt.pbl.

 

So – the quarry for digging up the existing Tess report defs is either  SampleFormats90.pbl or TessituraStandardReports90.pbl (but that’s not where Tess runs them from, that’s just a set of copies for you to play with, really); you need to make  a copy of the one you want to use as a starting point, and rename it (as you did), but then you should save your copy into a new library, and reference that library in your LOCAL_LIBRARY_LIST entry in t_defaults – and of course your Tess client needs to be able to see the folder that you use – using a folder path of  T:\User Reports\ is pretty much the standard way to do that.

 

 

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,

I wanted to have a look at modifying the d_mailing_labels object that Tessi uses in the User Defined Object From a List. From what I understand of the documentation and hunting around on TASK, when you select something like a label, it:

a) Looks up the object in T_FORMAT_INFO.

b) Then (and this is not perfectly clear in the documentation), I presume it goes and finds the D object (say, d_mailing_labels) from userreports.pbl?

Where I'm running into problems is that I can't find a userreports.pbl in our User Reports folder. The only .pbl that contains those label objects in question is one called SampleFormats80.pbl.

I tried a quick test, just by making a copy of d_mailing_labels and calling it ud_mailing_labels and getting the T_FORMAT_INFO to point to it. It didn't work.

So my questions are:

1. Where is the .pbl that the existing label objects are stored in and that any custom label objects need to be stored in?

2. Has it been renamed from userreports.pbl to something else, or have I got something wrong?

And maybe at some stage, it would be great to see some documentation added that explains clearly where labels need to be located to be referenced by T_FORMAT_INFO?

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!

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====