Aller au contenu principal



integration builder file method: Printing a different document based on name of dropped file name


2 commentaires

  • Avatar
    Seb Atkins

    We have accomplished this in the past by adding the document name (full file system path eg C:\Documents\document1.btw) that you wish to print into the csv file and then using that variable in the print document action we also do the same with the printer name so we can send different documents to different printers based on the data set.

    We create the csv file with our reporting software so we can create custom fields (printdocument and printername) based on specific criteria which in our case is normally the branch ID to decide which document/printer it needs to go to. I have provided a screen shot of our print document action, we are using a database integration (we just load the csv contents into a SQL database) but i would imagine you can do the same with a file integration.

    Hope this helps!

  • Avatar
    Peter Thane

    Hi Thomas,

    You can setup Integration Builder to look for various dynamic variable items were and pull those out from the trigger file. I have not used the name of the trigger file to determine the the label format personally (all those I have used have had the label format  name contained in the file) but the DetectedFileName is one of those so you maybe able to do what you want.

    I would suggest you check our Manny's webinar accessible from the Support home page as that talks about how address the variables and I found it very useful for the first few BT2016 integrations I was involved in configuring deploying,

    For ease the link the the webinar is below:

    I hope this helps



Vous devez vous connecter pour laisser un commentaire.