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

Question

Question

Laserfiche Scan Client Dynamic Fields Error: "Object reference not set to an instance of an object"

asked on November 3, 2016

I tried to use dynamic fields in Laserfiche scanning client and when I tried to select the child field, a error popped up (See error.txt)
 

But if I click clear all fields in the fields pane and select again I can easily access every dynamic field without the error popping up.

See the process below:

I click the Scan Client button:

I pick a value from my parent drop-down list:

Here is where it gets interesting.

I try to select a value from the child drop-down list and this pops up:

But then, when I press "Clear fields" in the bottom left of the Properties pane:

I can then select any Value from the child Drop-down list and it's child drop-down list:

Why is this happening?

error.txt (8.9 KB)
0 0

Replies

replied on November 3, 2016

Hi Freddie,

 

This rings a bell with older vesions of Laserfiche. What version are you using? If it's not V10 then please upgrade and it will likely resolve the issue.

 

Cheers!

0 0
replied on November 3, 2016

I am currently using version 10.1

0 0
replied on November 3, 2016

Ah ok. Do you see the same error across all the different scanning PC's? Do you see the same error when logging in to the problem workstation as a different windows user?

0 0
replied on November 3, 2016

Currently on testing server, happens on all users.

0 0
replied on November 3, 2016

The good old "object reference not set to an instance of an object" error is pretty generic and relatively meaningless, so you need to dig a big deeper. Check the windows event viewer for more information. Also it would be good to test connecting the scanner to a different PC and see if the issue still occurs as it could be workstation related.

0 0
replied on November 3, 2016

Okay will do. Any other advice?

0 0
replied on November 3, 2016

That will be a good starting point, as that will identify if it's workstation related. Also, has this ever worked or is this something that has just started happening?

0 0
replied on February 16, 2017 Show version history

I'm currently seeing this exact same behavior with a client running 10.1.1.320.  Has there been any resolution to this issue?

 

This only appears to happen when trying to use Dynamic Fields in the Scanning window.  Additionally, it only happens if I have more than 2 dynamic fields on my template.  Just to make sure it wasn't an issue with the data in my SQL table, I created a brand new table, brand new fields and a brand new template, but I'm still seeing this issue.  

Here is what my SQL table looks like:

 

 

And my template:

 

 

As you can see, nothing out of the ordinary here.

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

Sign in to reply to this post.