Error Initializing Custom Screen

I created a custom constituent screen in Infomaker and added it to TR_CUSTOM_TAB in the database. However, when I open up a constituent in Tessitura, I get the error message "Error initializing custom screen. Could not find dataobject *name of the custom screen*". We've used custom screens successfully before, and this screen is saved in the same library as the others; I'm not sure why Tessitura is having trouble finding or loading this one. Any ideas? 

Parents
  • In T_DEFAULTS, make sure for LOCAL_LIBRARY_LIST (for the field_name column) that in default_value the Infomaker library (.PBL file) containing the datawindow is listed, and the path provided is accessible from the client application. This is a comma delimited list of library paths.
     
    Example:
    c:\Tessitura\CustomReports\custom_reports.pbl,c:\Tessitura\CustomReports\SampleFormats100.pbl


    Another way of seeing what PBLs are accessible in the application is to load the "App Library" window under the Help menu.  There is a search filter at the top, where you can type in your custom datawindow and see if it shows up in the list.  If it does not, or is shown to be grouped under a different library file, then that is most likely an indication of version or file path issues.

     
    Hope that helps
    -Ryan
Reply
  • In T_DEFAULTS, make sure for LOCAL_LIBRARY_LIST (for the field_name column) that in default_value the Infomaker library (.PBL file) containing the datawindow is listed, and the path provided is accessible from the client application. This is a comma delimited list of library paths.
     
    Example:
    c:\Tessitura\CustomReports\custom_reports.pbl,c:\Tessitura\CustomReports\SampleFormats100.pbl


    Another way of seeing what PBLs are accessible in the application is to load the "App Library" window under the Help menu.  There is a search filter at the top, where you can type in your custom datawindow and see if it shows up in the list.  If it does not, or is shown to be grouped under a different library file, then that is most likely an indication of version or file path issues.

     
    Hope that helps
    -Ryan
Children