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

Question

Question

Parsing path for QF Universal Capture

asked on June 2, 2014

Using Universal Capture to import pdf documents, I want to use only part of the original path  as the path to send documents to. The pdfs are stored at G:\Property Transfers\Data\LEOPS\ plus at least two levels of subfolders. It's just the subfolders I want to retain to send the documents to. We are using QF 8.3.0 currently. 

0 0

Answer

SELECTED ANSWER
replied on June 2, 2014

It's because of the slash right before the opening parenthesis. The slash is a reserved character, so it's transforming the '(' into the parenthesis character rather than interpreting it as a beginning of a regular expression group. Same thing with the other slashes, they're interpreted as the regular expressions \P, \D and \L. Change all your slashes to double slashes.

 

G:\\Property Transfers\\Data\\LEOPS\\(.+)

1 0

Replies

replied on June 2, 2014

Good Afternoon Michael,

 

Do you happen to have Pattern Matching with your QF licensing? If so, then you could possibly use that to parse the path of the PDF's that you are importing and pull the data after \LEOPS\. You can then use the token created from the pattern match in your Store path.

0 0
replied on June 2, 2014

I've tried parsing out the data but I keep getting "Malformed \p{X} character escape" as an error. I've tried several different variations but nothing seems to be working.

TokenError.jpg
TokenError.jpg (50.76 KB)
0 0
SELECTED ANSWER
replied on June 2, 2014

It's because of the slash right before the opening parenthesis. The slash is a reserved character, so it's transforming the '(' into the parenthesis character rather than interpreting it as a beginning of a regular expression group. Same thing with the other slashes, they're interpreted as the regular expressions \P, \D and \L. Change all your slashes to double slashes.

 

G:\\Property Transfers\\Data\\LEOPS\\(.+)

1 0
replied on June 5, 2014

Thanks, it works great. I should have realized that the slash was a special character.

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

Sign in to reply to this post.