Question

'autocomplete' template values from list of previously submitted values.

Updated May 22, 2015

asked on May 22, 2015

I see it's possible to create a list of values pulled from a SQL Server table in a template dynamic field. So far so good. This works nicely.

Now, I've got this template field called ProjectName. Multiple documents often belong to a single project, so I'd like to suggest a project name in the template field based previously submitted values. So for example, if a project is called 'Area A OCP 2015' and someone has already submitted a document with that as a project name, that any subsequent documents would suggest a narrowing list of project names based on user input, so typing 'A' suggests every project name that starts with an 'A', 'Ar' every project that starts with 'Ar', etc.

Not sure what this might be called in Laserfiche (if anything), but other software sometimes calls this 'autocomplete'. I guess another way to ask is which table in SQL Server houses template field values. If I could point to that table, this would accomplish something like what I want. Not quite, but it would be close and would make for better data consistency so we don't end up with project names that are almost the same, but different like 'Area A OCP 2015' and 'area A ocp - 2015' etc etc.

See what I'm saying?

0 0

Replies

replied on May 22, 2015

Hi Dale,

We have this as a feature request and will look into it for a future release.

Thanks

0 0

replied on May 22, 2015

Ah, very good. Thanks for replying anyway, Alexander. For good data consistency, a builtin autocomplete will be a great help.

How about my second favorite option then of linking a table in SQL Server? Are the template values stored in a single table somewhere that I can link to for previous values? This isn't quite what we're looking for, but would still be an improvement over free forming the project name every time.

0 0

replied on May 22, 2015

The field values are stored in the propval table.

One possibility may be to create a new external table based off of the distinct project names currently in the propval table. Then have one field set as a dynamic field linked to that external table so that they can select from the existing project names. Then have a second field in the template that allows for the option to enter in a new project name if it's not in the first list. Using Workflow you can then check that if that second field is filled in, to use one of the SQL activities to insert it into the external table, thus keeping it up to date.

0 0

You are not allowed to follow up in this post.

Question

Question

'autocomplete' template values from list of previously submitted values.

Replies

Sign in to reply to this post.