EngageOne™

 View Only

  • 1.  Check if Lookup Table File is Empty

    Posted 04-13-2021 11:35
    Is there an entry in the OPS file or while building the HIP that can be used which will prevent the .HIP from executing if the file for the LookupTable is empty (file size = 0 in a Linux environment).

    Secondly, is there an action we can take in Designer where eveytime we perform a textsub lookup and we get the following warning message:
    GEN0625W No match for LookUp Table label '%1' in file alias '%2'

    we can keep track where in the logic the lookup failed and display specific fields for debugging purposes.

    Thanks.
    Neville Bhacka

    ------------------------------
    Neville Bhacka
    United Parcel Service
    Morristown NJ
    ------------------------------


  • 2.  RE: Check if Lookup Table File is Empty

    Posted 04-14-2021 08:33
    Hi Neville,

    regarding
    1.) ​you can run a DOC1PCE Script before your actual DOC1GEN to check if file is empty. Besides I think under linux you should be able to evaluate filesize in shell script and control doc1gen accordingly.

    2.) Have your lookup-function return the value into a variable (strResult) )and check if  <strResult> IS SET and <strResult> <> "" (no blank in condition logic). it will be "" when match not found. You can then print message any trace information you like i.e. with a global active content.

    Regards,
    Marc

    ------------------------------
    Marc Seidler
    BSG Business Services GmbH (VAR)
    Bielefeld
    ------------------------------



  • 3.  RE: Check if Lookup Table File is Empty

    Employee
    Posted 04-14-2021 11:15
    Hi Neville.

    Regarding tracking the logic map item and position where Generate reports warning messages , such as lookup table failures.

    This can be achieved by enabling the Generate Trace settings.

    You can enable these in the Designer Publish Wizard / Production Job "Advanced / Diagnostics / Trace Information" section when Publishing for Generate , but you may prefer to enable these only in the Generate Override Production Settings (OPS) file as required.

    The Generate Trace OPS Settings required to give the logic name for Generate errors (including your quoted lookup table error) are ;

    <Trace>
    Outputfile=/path/GenerateTrace.log
    TraceLevel=Complete
    OutputCodepage=UTF8
    memlimit=0
    Supporttrace=on

    You may also find the it useful to re-execute only the specific dataset(s) that report the relevant error using

    <Advanced>
    RangeOfPublications=NumberedListOfPublications ; Example 1-3 , 1,5 , 500+, etc

    Note that enabling <Trace> for all executions does necessarily involve extra processing and output file creation , so will have a performance impact.

    Hope that Helps.

    Paul Barron

    ------------------------------
    Paul Barron
    Principal QA
    EngageOne Compose (Designer / Generate)
    ------------------------------



  • 4.  RE: Check if Lookup Table File is Empty

    Employee
    Posted 05-25-2021 12:51
    Neville... you can use the Action "Print Message" inside your logic map to write messages to the Generate log. Messages can contain fixed text, variable data values etc. etc. For example, many clients write some unique value at the start of a Publication, e.g. account number or customer reference to the log using the Action "Print Message". Also, writing the name of the logic map Bundle or the name of each Active Content to the log can help track where in the logic map the processing has reached just prior to the failure. You can choose to execute the Action "Print Massage" from pretty much anywhere in the logic map - you decide.

    ------------------------------
    Alan Hunter
    Pitney Bowes Software Inc.
    Troy NY
    ------------------------------

    Original Message