Integration Builder - Job Name not passing to output file Seguir

0

Hi

We have several integrations using %DetectedFileNameWithoutExtension% and job name checked to process PDF file outputs via Bullzip PDF printer. This has worked well for us to date but for some reason my new integration is ignoring this setting and outputting the filename as the btw filename each time.

Ive checked the settings side by side with a working integration and they're identical. I also created the btw file again from scratch just in case. Still the same.

 

Any ideas where IM going wrong? Thanks.

4 comentarios

0
Avatar
Xabier Clemente
Moderador
Acciones de comentarios Permalink

Hello Matt,

Welcome to the forums!

That variable is the name of the trigger file, so if your trigger files are named the same as the .btw document, then it will appear that the .btw doc is the filename. Bullzip's settings are global. Integrations cannot change them. So it's likely something with the trigger filename is causing this issue.

Do you see something out of the ordinary on the logs when compared to the integrations which are running fine?

Perhaps we can find our answer there.
0
Avatar
Matt Rogerson
Acciones de comentarios Permalink

Hi,

Thanks for your reply.

The incoming filename has a filename structure of 'SHPVEHICLEMAN_*.txt' where we suffix with a unique number. Just to be sure, I changed the btw file to VMShipLabels.btw to fully differentiate the two. Still it outputs as VMShipLabels.pdf

 

I have another (working) integration which I have checked side by side with this one that works perfectly. Structure is 'VEHICLEMAN_*.txt' and btw file Vehicle Manifest.btw and outputs as VEHICLEMAN_xxxx.pdf

Cant see anything out of the ordinary that would mean one works and the other doesnt and Ive recreated the integration several times, copied the working one and updated some of the trigger and file location fields etc

0
Avatar
Matt Rogerson
Acciones de comentarios Permalink

Could it be a setting in the btw file? Ive checked and cant see anything obviously different from the working integration.

0
Avatar
Matt Rogerson
Acciones de comentarios Permalink

Just a quick update in case this helps anyone else in the same position. I basically recreated and tested the integration and bartender file field by field and it worked as expected right up until I added  a new text entity type: 'Print Job Field' field: 'Total Number of Records'.

For some reason, the minute that was added, it defaulted to save as the BTW filename rather than the detected file name. Deleting this field then made the integration work again.

Not sure if a known bug in Bartender or expected behavior but its been a real headache.

Iniciar sesión para dejar un comentario.