Skip to main content

Today I’m having difficulty in merging documents into one PDF. We aren’t looking to generate a document using the tagger feature. So it should essentially loop through images (.png or .jpg) or pdf files (already in pdf) and make them one combined PDF. 

 

It’s pretty straightforward. However, I’m receiving the following error:
 

I noticed there was an old article recommending removing special characters. 

Doc Generation - An error occurred downloading a file... | Community (nintex.com)

 

I have removed special characters or ones I thought may be restricted for this action anyways which where parenthesis. “()” have been removed from all files before uploading since we can’t rename list item attachments within workflow designer.

 

It didn’t work. My list item attachments are as followed:

 

What am I missing? Why will these not convert to PDF? 

 

Also, which special characters are prohibited for this action? There is no help documentation that covers this! I would think acceptable characters would align with what SPO allows in a library etc or on a list item attachment to avoid issues. We can’t rename list item attachments, so it will need to align for sure with those. 

 

I have done several tests for this issue on a separate test site. I was able to replicate the issue and narrow it down to the PDF files for the process I’m troubleshooting for a citizen developer:

  • Test #3: Word documents I upload are working fine.
  • Test #4: PDF files I upload are working fine.
  • Test #5: PDFs from the process I’m troubleshooting are failing.
  • Test #6: Images I upload are working fine.
  • Test #7: Images from the process I’m troubleshooting are working fine.

Something with the PDF files from the process in which I’m troubleshooting seems to be hanging up the system and would like to know why or what is the issue. I have logged a support ticket but this behavior seems strange.

 

 

 

Hi @brandiwoodson 

 

where do the failing files originate from? Are they being created by another application or are they generations from another workflow? 
 

The reason I ask is that there are some cases where some applications use really old PDF libraries to create PDFs which can result in this time of error. 
 

Jake 

Honestly, I have no idea where they originated from. I know they are being uploaded into SPO as a list item attachment. But where they came from before that - no clue. I have logged a Nintex ticket and reached out to the user who built this process that was asking for support. I advised that the action is working fine as-is, since we added that to his workflow last week, but that the specific PDF file he was using for testing is not working as expected. 

 

I will have to connect him and a nintex support rep together to figure out the root cause of that one file. I will pass along this information to the support rep. Thanks!

Hi @brandiwoodson 

 

Does seem to sound like it, one way to test would be to open the failing files, print them to PDF, not save and see if this corrects the issue, printing will reformat the files. 
 

Jake

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings