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

Question

Question

Quickfields - How can you fill doc metadata with Lookup results

asked on January 14, 2020 Show version history

It says in the Lookup object help file:

"The tokens generated by the Lookup process can be used to fill out document metadata such as document name, folder path, and fields."

The lookup object creates a token in testing but the lookup objects are ignored in the token dialog. So how would you ever get the result of the lookup into the metadata fields?

This is the lookup object

Here you can see it generates a token

But since Lookup objects are always filtered out of the token dialog, where would I ever be able to use this data?

Your never going to be able to access any of your lookup activities in this menu

Or this menu

 

Update: I just remembered that you must select which columns your query is going to return before you write the query. The documentation does not mention this at all, it even says selecting a table and columns OR writing your own custom query which is not true.

This is not like workflow where you can just write the query, then test, then access the resulting column data as tokens.

I still have the same problem though, because we are querying from something that is not in the list of tables.

0 0

Replies

replied on January 14, 2020

Hi Chad,

To reference the tokens returned by a custom query in Quick Fields, you can manually type the token syntax wherever you want the token value to appear. The syntax to use here would be %(Lookup Process Name_Column Name). You'll want to replace "Lookup Process Name" with the name of your lookup process in Quick Fields, and "Column Name" with the name of your table column. Using this syntax, you should be able to retrieve the values from the query, even if you don't explicitly choose which columns to return in your custom query. More information about this syntax and how to set up the query can be found in our help files here.

0 0
replied on January 14, 2020

Awesome I will give this a try tomorrow morning! 

0 0
replied on January 15, 2020

Tried this morning and it will not take either Process Name_column name or Column.column name as recommended in the help files

Here is the output

But it is not allowing any of the syntax

0 0
replied on January 15, 2020

Hi Chad, did you try running the session? Sometimes it will highlight the token syntax in red if it was manually typed, but still successfully fill in the tokens when the session runs.

1 0
replied on January 15, 2020

Yes but it doesn't even try to read it. It just plugs my literal syntax directly into the field value.

0 0
replied on January 15, 2020

Is your lookup process under Page Processing in the document class?

0 0
replied on January 15, 2020

Yes and even if I add a Create Token Values beneath, it does not give me any access to the Lookup object unless I specify which fields are going to be returned which is impossible if the table does not exist in the list of tables.

0 0
replied on January 15, 2020

Oh, wait, so you are going with a custom query and manually typing the tokens in?

In that case, this is expected behavior. They will not be considered valid at design time, but will be populate with values at scan time, provided they are in the right format and the query returns values for them.

0 0
replied on January 15, 2020

Ah, got it! I guess when I tried running it I was still using the help documentation syntax Column.[columnname]. It works when I use Kathleen's syntax [objectname]_[columnname] and then scan. This will do the trick, thank you both!

0 0
replied on November 15, 2020

There's a typo on this page: https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/QuickFieldsAdmin/Content/Processes/Lookup.htm

Tip: When writing your own query, the token format to use is %(Column.ColumnName) where Column is always the same and ColumnName is what your query specifies. For example, select X as Y from Z would produce a column named Y, so the token would be %(Column.Y).

 

This %(Column.ColumnName) format seems to be for Real-Time Lookup only. Whereas for the regular Lookup process, the format is %(LookupProcessName_ColumnName).

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

Sign in to reply to this post.