You are viewing limited content. For full access, please sign in.

Question

Question

Pattern Error - Fill out PDF

asked on November 28, 2016

Hi, I am using pattern matching in a table in my Fill out PDF action. It fills out correctly but gives me a few warnings. I was wondering if anyone else experienced this?

I have even rebuilt the action hoping that the warnings would go away, and also rewrote the PDF but the same issue remains.

 

On this pictureyou will see the warning message, the result of the action - top right filled out PDF, and the original form to confirm that the entries are correct - bottom left.

 

Here is my Table setup, I am using "Date_" because I have "Date" as date of submission.

0 0

Replies

replied on November 28, 2016

Are your patterns only returning the first result?

 

0 0
replied on November 28, 2016

No, that is the weird part - everything gets filled out properly so i am not sure why I am seeing the warning. 

0 0
replied on November 28, 2016

The warning usually comes up when you have multiple fields with the same name in the PDF. It's hard to say from the screenshot if that is the case for any of the fields shown.

0 0
replied on November 29, 2016

But they are all their own unique names, otherwise the pattern wouldn't even work or it would have duplicates, right?

0 0
replied on November 29, 2016

I meant within the same group. If you have 2 fields called Date_2, they'd both match the pattern, but you'd get that warning because Workflow wouldn't be able to tell which one should be first, so it might end up putting the data in the wrong one.

0 0
replied on November 30, 2016

Yeah, I know what you mean I think - here is the screenshot of my PDF, as you can see all are unique (Name and tooltip match so they are all distinct). I have replaced the PDF several times and not sure what else to try because I am getting a warning but no duplicate values, everything populates correctly.

0 0
replied on November 30, 2016

I get this all the time when I use workflow to fill out PDF tables.  Since it always filled out correctly my best guess has been that the error is because it is trying to fill all the table rows.  So if your form has 10 rows but it only fills 3 of them, I see the error.

You could always test the theory by putting a new PDF in there with only 3 rows (like your example) and retry the workflow using the same data.  See if you still get the error if there are no empty rows.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.