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

Question

Question

Intellisense in Dynamic Fields update in 10.2

Laserfiche
Updated July 28, 2017
asked on July 10, 2017

Hi there,

We have been using the intellisense for dynamic fields inside a template as discussed in the below thread for some of our clients. This allows us to start typing in a field, bring up a list from a lookup but also type in and save the field as a new record inside this.

https://answers.laserfiche.com/questions/68091/Using-Intellisense-in-the-template-fields

The issue is upon updating to 10.2, I receive the error "Dynamic Field Validation has failed".  I've been told this is a bug fix and will no longer function.

Does anyone have a workaround or a way to replicate the functionality?

0 0

Replies

replied on July 10, 2017

Hi Alex,

I'm curious--does your lookup table contain a column of type DATE?

What I've noticed recently is that I receive an error when trying to link to tables with DATE columns, but I do not get the same error when I recreate the table using DATETIME instead of DATE.

I don't know if this is related at all to your issue, but it's the first thing that came to mind after reading that your client's dynamic templates suddenly do not work with their external tables.

~Rob

0 0
View 1 previous reply
replied on July 11, 2017

Hi, Unfortunately the only column I have in this table is a nvarchar column. It works fine in 10.1 but completely breaks as soon as I update.

0 0
replied on July 27, 2017

Alex

I just ran into this issue. I found that the issue with the validation was the dash I had in the GL code. I removed all the entries with dashes in the in the field and the error went away.

 

I am not sure if you have the opportunity to modify the data directly. I would think a view could be built removing all the dashes in the field and use that for your external table.

 

I did also test it was not all special characters as I replace the: - with a * and it saved, reverted back and failed.

1 0
replied on July 27, 2017

Alex

I mis spoke on multiple characters the * does not work. I must have not went out of the template when testing.

0 0
replied on July 28, 2017 • Show version history

Unfortunately it still brings up the error, even when I try creating a new repo + fields from scratch. The bug fix is super effective. My current workaround is just showing the customer on Web Access and having The Client on an older version, not optimal.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...