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

Question

Question

Export values from List Field in LF Cloud

asked on March 14, 2022

So here's one for those that like to find creative solutions.  I'm working with a customer that uses LF Cloud.  I'm running several documents through Quick Fields, which is using barcodes to identify the document type, then assign that value to a list field.

I would like to be able to have Quick Fields verify that the value it gets from the barcode is a valid value that exists in the list field in order to prevent false identification if a barcode happens in the document organically (other than on the cover sheet) so it doesn't create a new document with an invalid value for the field.

Since it's Cloud, I can't just set up the LF database as a data source to do a token verification against.  I thought of using Cloud Workflow to get the values and update a local SQL database, but I can't find any activities capable of pulling all available values from a list field.

Any ideas?

0 0

Replies

replied on March 14, 2022

You should be able to use a Lookup Table in cloud to populate the template field list and then use the Remote Agent to sync the lookup table with the local table.

3 0
replied on March 15, 2022

As far as I can see, a lookup table is basically just uploading a spreadsheet to the cloud for use as a data source.  That still requires manual updating any time there's a change to the list.  While that would work, it's really no better than manually maintaining a SQL table that Quick Fields can access.  What I'd really like to do is have a way for Quick fields to accurately know what the list field options are without a lot of behind the scenes maintenance.  The only way I can see to do this would be if Workflow could pull the values from the Laserfiche configuration.

The killer of it is, Quick Fields already does this kind of validation, but only AFTER the field is filled in by the page processes, which invalidates the document and won't allow it to be stored if the value isn't valid.  I just want it to look at that BEFORE it splits the document based on an invalid value.

0 0
replied on March 14, 2022

Have you looked into using a Remote Agent to update/sync a local SQL table with your Cloud list field?

0 0
replied on March 14, 2022

Yes.  I have that part down.  The catch is, how do I get cloud workflow to pull those values to send to the agent?  I can't seem to find a way to get it to read up the values.

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

Sign in to reply to this post.