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

Question

Question

Quick Fields Token - adding spaces where a \n used to be?

asked on August 11, 2016

I am getting QF to grab an address out of a long set of lines, where (in this case) the address is only three of those lines.  It has grabbed the three lines, but I want QF to place them all on one line, into one field, but this is what I get:

PLAN RN67 (LXVII)BLOCK 3LOTS 25 AND 26, where what I want is

PLAN RN67 (LXVII); BLOCK 3; LOTS 25 AND 26, or at the very least

PLAN RN67 (LXVII) BLOCK 3 LOTS 25 AND 26.

How can I get QF to change the field results to what I want?  (The letters/numbers of the three lines will always be different for each page it runs on.)

0 0

Replies

replied on August 11, 2016 Show version history

One good way is to use the token editor, check the "Apply Index" with "All values separated by" option and choose to separate them by a space or semi-colon. 

1 0
replied on August 11, 2016

Thanks, Tessa!  That should have worked.  But... I'm not getting good results yet.  I made the change and ran it on two documents.  One I got the exact same result as reported above (the three target lines smooshed together); on the second document, I got the entire OCR grab, instead of just the pattern match result only.

The Pattern Matching grabs the right details:

But the Field Token Editor does not:

I believe part of my problem is that the test run is fine, but when you actually do the QF run on the documents, the field token is not always taking just the pattern match, it's taking the entire OCR results (which is a lot more!).  Any ideas what to do about that?

And on the other one, probably what happened is it actually returned the right answer, just not separated again, because even though I told it to return each line as a multi-value item, it has not done that, it has returned all three lines as one value with no separation.

0 0
replied on August 11, 2016

Hmm. Hard to say exactly what's happening without the documents and session in front of me but I recommend focusing on one document at a time and taking a look at the output pane and seeing if you can find any clues there. 

 

When you see it giving you the entire OCR results instead of just the pattern, that probably means that a matching pattern wasn't found in the text, and you have this option checked:

So playing with those options might also help you troubleshoot. 

0 0
replied on August 11, 2016

That's right, that's what I have it on.

0 0
replied on August 15, 2016

Tessa, is there anything else I can check or change? 

0 0
replied on August 15, 2016

Can you check the output pane results for the relevant tokens as well as the resulting field value? This will give us clues as to what step is going wrong. 

0 0
replied on August 15, 2016

Okay, in today's test run I got the following in the Legal Address field: 
PLAN 9523777
BLOCK A
LOT 1
CONTAINING 1.15 HECTARES( 2.84 ACRES) MORE OR LESS
Oh, that's interesting!  When I cut and paste it, it remembered the carriage returns!  What actually shows in the field is:

Okay, now for the output pane info you asked for... oh, it was exactly as the cut and paste result was!  And the tokens:

      

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

Sign in to reply to this post.