invalid object name again

replied on April 21, 2016

quick update, I got it to store after I changed the file name to test, so what in the file name caused it to not store, and don't say a newline character because there was none in there.

0 0

View 6 previous replies

replied on April 21, 2016

Hi,

From the output you showed, it looks like there's some character causing a new line here:

Even if your regular expression is already filtering out newline characters (\n), it may need to also filter out carriage returns (\r).

One good way to check for both characters is by copying and pasting the text from the output pane and then pasting it into the test area for the pattern matching process, and checking the box that says "Show line break characters as \r and \n", like so:

0 0

replied on April 22, 2016

Have you tried formatting the date differently? Maybe the / is causing problems. For sorting purposes, I always try to apply the formatting yyy-MM-dd to all my dates if I use the date in the name of the file.

0 0

replied on April 22, 2016

Why does my QF not have that option? There is no box that is show line break characters. That would be nice to have.

0 0

replied on April 22, 2016

I'm also having trouble finding the .bxd file. Can you help with that too?

0 0

replied on April 22, 2016

If you're applying the regular expression from within the Token Editor, that may be why you don't see that checkbox. The checkbox should be there if you apply the regular expression from within the 'Pattern Matching' process.

If that doesn't reveal the problem and you want to look at the .bxd file for more clues, you can find it by looking in ProgramData\Laserfiche\Quick Fields\Files\[Session ID]\bxd. The session ID will be a string of numbers and letters and it will likely be one of the most recently modified ones.

0 0

replied on April 22, 2016

I have looked at BXD files before but the check box for line break characters would be awesome. I tried with the wizard and I still don't have that box. I added a new pattern matching process and again I don't see that box. Is that a feature of QF10? If not can you made give me more of a step by step to get to it. I would find that feature really helpful. Thanks.

0 0

replied on April 22, 2016 • Show version history

Ah my mistake, you're right - that checkbox is in Workflow 9.1 but not in Quick Fields 9. But it will be in Quick Fields 10

In the meantime, an easier method than using the bxd file might be to just copy output from the output pane and then paste it into any editor that will reveal line break characters. For example, notepad++ can do this if you go to View -> Show Symbol -> Show end of line.

0 0

replied on April 22, 2016

oh ok, I'll test that. I always take the output from the OCR boxes to test the patterns, so no I'll try taking the output from the pattern matching to check for line breaks.

Follow up question: If line breaks are so troublesome to QF, why does the software even capture them? I cant think of a time where I wanted a line break in a token.

0 0

replied on April 22, 2016

Well, we don't want to start ignoring them in tokens altogether because then users wouldn't be able to define patterns that rely on them - for example, capturing all the text after a line break.

However, I definitely hear you that this situation can be tricky. Part of it is due to a known issue regarding the fact that you have to specifically filter them out in your regular expressions. Furthermore, we're also looking into other ways to make line breaks less troublesome.

2 0

Question

Question

Replies

Sign in to reply to this post.