Precisely Enterworks

 View Only
  • 1.  Scheduled Exports with Export Template with output type of json

    Posted 10-13-2023 15:56

    Hi All,

    hoping to get a little guidance with something.  we use a Sch Export with an Export template with an output type of json - exporting data for each Product from 9 different repositories.  we would like to export another data point for each Product that is not an attribute but would be a concatenation of two attributes already being exported.

    is this possible?

    i've looked at the Tech Talks 101 and 116 - however, it appeared that the output type of json was limited to adding something to the end of the file (one time) instead of adding something for each Product record in the file.

    anyone have any suggestions other than adding an attribute to the Product repo.

    thank you!



    ------------------------------
    Ruthy Sleeth
    PIM, Product Owner - IT Operations
    New Pig
    Tipton PA
    ------------------------------


  • 2.  RE: Scheduled Exports with Export Template with output type of json

    Employee
    Posted 10-15-2023 17:43

    Ruthy,

    There are several different avenues you can consider:

    1. Define the attribute that is the concatenation of the other two attributes and use VTL or Change Notification (the latter required if those two attributes are not in the same repository) to keep the concatenation attribute in-sync.
    2. Switch from JSON to a tabular (CSV, XLSX) format and then use Publication Callout to implement a stored procedure that inserts the concatenation column into the staged publication results table and then populate the column with the concatenation of the source columns (and optionally drop the source columns from the staging table if they are not needed for the final output).  This would require any receiving system to process a CSV (or XLSX) file instead of JSON.
    3. Implement a Scheduled Export post-processor that reads in the generated JSON file and added the new field to the appropriate locations to concatenate the two source fields together.

    Of these options, the first would be the easiest to implement and the main cost is mostly additional (and redundant) storage in the database.

    -Brian



    ------------------------------
    Brian Zupke
    Precisely Software Inc.
    ------------------------------



  • 3.  RE: Scheduled Exports with Export Template with output type of json

    Posted 10-16-2023 08:01

    Thanks Brian!

     

    Ruthy