Unable to open library

Good morning to you!

The library file is most likely read-only.  These report datawindows should really be copied to your own local reports library with a different local naming convention.  This library exists as a starting point for custom reports and should not be referenced directly in the Tessitura application.

Best of luck!

______________________________________

Ryan Creps

Network Developer |Tessitura Network, Inc

Good morning,

I am in the tessiturastandardreports80.pbl and trying to modify one column to make it invisible. However when I click save I get an error message stating it is unable to open the library. What am I doing wrong?

Thanks for your help!

Naomi

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!

Checked by AVG - www.avg.com
Version: 8.5.387 / Virus Database: 270.13.17/2242 - Release Date: 07/16/09 18:00:00

When a standard report runs in a “System Window”, there is an intermediary application window that is used to render the datawindow.  This allows Tessitura to perform additional steps and manipulation to the end report output, many things not functional in the standard datawindow.  In order to adapt the datawindow to work with the standard reports window (used when Window Type in Report Setup is set to “Infomaker”), you need to make sure that a few things are in sync:

1.       The datawindow retrieval arguments match the parameters from the Report Setup.  Sometimes these are in a different order because they can be rearranged in the application window script.

2.       The datawindow stored procedure is associated to the custom stored procedure

3.       The datawindow column specifications match the resultset of the stored procedure (or SQL query if using a stored query).

4.       In order for parameter values to display correctly, the text object names may need to be modified (like changing st_season to st_p1, for instance).

Every report is obviously a bit different.  These are general guidelines for adapting standard reports.  The other thing to note here is sometimes an application window will be used to toggle between one or more datawindows, all which make up the “report”.  Because this is done in the application and not in the datawindow, a custom solution will be necessary if you wish to replicate that functionality/feature.

Hope that helps.

Best,

______________________________________

Ryan Creps

Network Developer |Tessitura Network, Inc

Ryan,

I moved the reports over to our custom library however this particular report runs in a system window can you provide me guidance on how to get this to run in our custom library. The report is Performance Sales Summary. I have moved over all the reports and the report setup but I need to point it to a different system window, which is where I need assistance.

Thanks!

Naomi

Naomi

When a standard report runs in a “System Window”, there is an intermediary application window that is used to render the datawindow.  This allows Tessitura to perform additional steps and manipulation to the end report output, many things not functional in the standard datawindow.  In order to adapt the datawindow to work with the standard reports window (used when Window Type in Report Setup is set to “Infomaker”), you need to make sure that a few things are in sync:

1.       The datawindow retrieval arguments match the parameters from the Report Setup.  Sometimes these are in a different order because they can be rearranged in the application window script.

2.       The datawindow stored procedure is associated to the custom stored procedure

3.       The datawindow column specifications match the resultset of the stored procedure (or SQL query if using a stored query).

4.       In order for parameter values to display correctly, the text object names may need to be modified (like changing st_season to st_p1, for instance).

Every report is obviously a bit different.  These are general guidelines for adapting standard reports.  The other thing to note here is sometimes an application window will be used to toggle between one or more datawindows, all which make up the “report”.  Because this is done in the application and not in the datawindow, a custom solution will be necessary if you wish to replicate that functionality/feature.

Hope that helps.

Best,

______________________________________

Ryan Creps

Network Developer |Tessitura Network, Inc

Ryan,

I moved the reports over to our custom library however this particular report runs in a system window can you provide me guidance on how to get this to run in our custom library. The report is Performance Sales Summary. I have moved over all the reports and the report setup but I need to point it to a different system window, which is where I need assistance.

Thanks!

Naomi

Naomi