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

Question

Question

invalid object name in Quick Fields

asked on February 10, 2016

I have a customer that keeps getting Invalid Object Name when trying to store documents in QF. its wired because there is not much to go off of to find the actually problem. I found a post that said it could be the file names but I looked at them and they are no different than current file names that have already been saved. She ran a batch and half of them did this so its not like they all failed. Here is what they look like. Any idea of where to start trouble shooting would be great. 

 

 

0 0

Answer

SELECTED ANSWER
replied on February 12, 2016

You might be getting some extra characters in there from OCR, maybe a tab.

Try 733-5423.*\n(.*)\s+\[\d+\]

Though, I'd still make it safer by specifying there shouldn't be newline characters in the match group: 733-5423.*\n([^\n]+)\s+\[\d+\]

1 0

Replies

replied on February 10, 2016

That usually happens when you have trailing spaces in the folder or document name. If you click in to the Document Name or Folder Path editbox and press "End" is there extra space between the last visible character and where the cursor is?

0 0
replied on February 11, 2016

So check for blank spaces and didnt find any. What else shoudl I look for? 

0 0
replied on February 11, 2016

Sorry, I can't quite tell what's what in the blob of text below. If it's not trailing spaces, it could be either unprintable characters or newline characters in either the name or the path. They usually come from Zone OCR reading multiple lines and regular expression in Pattern Matching being less restrictive than needed and including them in the value.

They're not easy to find, you would have to open the document's XML file in a text editor that renders them, like Notepad++. The files would have extension .bxd and be located in subfolders in <ProgramData>\Laserfiche\Quick Fields\Files\<Session ID>\bxd.

For ex, if you see something like in the screenshot below, the folder name has a newline in the middle so it would be invalid:

A proper one would be on a single line:

If you open the application errors pane (F12) and copy the details of the "Invalid object name" and paste them here, it might give us a better idea whether it is the folder or document name.

0 0
replied on February 12, 2016

so that is the issue. This is what I'm getting. 

 

How do we resolve the issue?

0 0
replied on February 12, 2016

With QF closed, take out the line break between the \and "AM Conservation...", save the file and reopen the session. That will allow the existing docs to be sent.

Where is that value coming from?

0 0
replied on February 12, 2016

Just like you explained, its a token coming from a regular expression. This customer deals with a shifting issue on her AP paper work and a small OCR zone box is not working. I instead went with a larger zone and made an expression to capture the vendor name. The zone always gets the top of the paperwork which the last line of text is a phone number. The regular expression is set to capture everything after that. The vendor name is lower then the phone number so it must be grabbing the line too. This is what it looks like.

I'm trying to get the regular expression but quick fields wont let me edit the pattern matching configurations or anything for that matter. What is preventing me from editing the session?

 

 

0 0
replied on February 12, 2016

ok, I restarted Quick Fields and got it. 

Is there anything i can do to the pattern to not capture the line break?

 

0 0
replied on February 12, 2016

I think if you change it to 733-5423.*([^\n]+)\[\d+\] it will do what you want. The capture group now specifies anything but a line break ("\n") and allows for extra lines between the phone number and the company name.

0 0
replied on February 12, 2016

Perfect, that's what I needed. Thank you. Ill let you know how it goes. 

0 0
replied on February 12, 2016

When I tested yours in the token editor, it wasn't working. I put the ( in front of .* and the testing seamed to work but its also looks like its adding spaces. I reran the document with your and my new expression with no luck. Yours returned no value, mine got the vendor name but its the same problem again with blank spaces. 

0 0
replied on February 12, 2016

ok, I feel like I'm going crazy here. I copied the text out of the Zone OCR so that I can test the actually text the the box is retrieving. I past that into the token editor so I can test my expression with quick fields. This is what it get. 

Looks great right? Also I have been testing in Regex101.com here is what i get from them.

ok, now here is what happens when I run the session on my document.

Vendor Name3 is my token... I'm completely  stumped. Please help!

0 0
SELECTED ANSWER
replied on February 12, 2016

You might be getting some extra characters in there from OCR, maybe a tab.

Try 733-5423.*\n(.*)\s+\[\d+\]

Though, I'd still make it safer by specifying there shouldn't be newline characters in the match group: 733-5423.*\n([^\n]+)\s+\[\d+\]

1 0
replied on February 16, 2016

Hello again, your expression seamed to work great in regex101 and in the token editor testing. When I run the sessions everything looks great too. The issue it still there though. whats really weird is that all the fields looks great but this is what I get from the Notepad++

as you can see in folder path, there is no line break but there is also no vendor name, even though that field is being populated. What does that mean?

0 0
replied on February 16, 2016

here is another one i just did.

0 0
replied on February 16, 2016

Which one? The first or the second one above. It might be easier to just open a support case and attach sample images at this point...

0 0
replied on February 16, 2016

they are both the same scenario. I attached the screen above the shots of Notepad++ becasue I wanted to show you that the Vendor Name field is showing correctly in QF but when I open the BXD file, it shows that field is empty. Am I seeing that correctly or am I missing something?

0 0
replied on February 16, 2016

I can't tell without seeing the regular expression and the data from Zone OCR. There are some known issues with the handling of newline characters in the Test Pattern dialog.

0 0
replied on February 16, 2016

Ok, were done! It worked all of a sudden. I restarted QF and reran some testing because I wanted to show you the BXD file and when I was looking at it, everything looked the way it was suppose to.  I tried to store the file into Laserfiche and it saved without any errors. Thanks for sticking this out with me. 

1 0
replied on February 11, 2016 Show version history

So I double checked with the user and there is no blank spaces at the end of the folder path or the file name. I even copied the error log off the machine. Here it is. 

 

Information    12    Date Zone : Dec-14 ` to  Jan-13
vzw
Surcharges E. Taxes,
Equipment Other Charges Governmental
Charges & Credits '.Surcharges & Fees TOTAL hedge
1.51 1.84 $32.19 102012010C    Date OCR        -1    
Information    13    Date Zone : Dec-14 to  Jan-13
vzw
Surcharges & Taxes,
Equipment . Other Charges Governmental
Charges &Credits Surcharges&fees TOTAL Budgr
1.74 2.17 $51.98 102019190(    Date OCR        -1    
Error    14    Invalid object name.        
Verizon Wireless (1)  - 220504 - 2/01/2016    0    Checks
Error    15    Invalid object name.        
Verizon Wireless (1)  - 220504 - 2/01/2016    0    Checks

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

Sign in to reply to this post.