Zum Hauptinhalt gehen



Print Command Script via Integration does not put DB data into the correct fields


1 Kommentar

  • Avatar
    Casey Hebding

    After digging into this issue further, I was able to resolve it. It seemed to have to do with the data source. I was using the same file as the data source for the Bartender template and the command script data source. For whatever reason this caused the behavior with the fields being messed up.

    To resolve this, instead of connecting the Bartender template to a dynamic csv text file, I instead just used "embedded data" and kept the command script pointing to that csv file. Now I do not run into the problem anymore.


Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.