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

Question

Question

Lookup Table vs Lookup Query

asked on June 25, 2024

For on-prem systems, I am able to use the external table as a lookup source and run my rules from there (If field A matches column A, fill field B with column B). I can configure and reconfigure those individually as needed on the form. In cloud, it appears that I can only use a Lookup Query as a lookup source, where the rules are pre-configured. This means that I would need to set up a Lookup Query for every possible combination of information that I would need, which would make doing what I need to do impossible since there are many tables in the database.

Has anyone found another way of doing this? I am building a case management system but the loss of this feature would mean scrapping the project or moving to another product.

image (98).png
image (97).png
image (96).png
image (95).png
image (94).png
image (98).png (31.53 KB)
image (97).png (17.78 KB)
image (96).png (34.48 KB)
image (95).png (25.86 KB)
image (94).png (20.62 KB)
0 0

Replies

replied on June 25, 2024

You do need a lookup query to use in WF or Forms in order to actually retrieve any data from your lookup table. What I have done in these cases is add all columns as outputs so the invoker can determine which fields it wants to use. The issue is really in the "where" clauses of the rules, lookup rules right now do not have optional parameters so if you query by employee id in one form, and employee id and email in another you will need two rules.

That being said, we have a feature in beta right now that allows you to use the Laserfiche API to query lookup tables from JS in forms designed with the new form designer. If these forms are using the new designer would you be interested in joining the beta for this feature?

 

We are currently looking into 

  1. Having "simple rules" configurable from the lookup rules page without requiring a lookup rule
  2. Being able to have optional parameters or actually add additional where clause parameters when configuring the lookup rule

 

If you could provide one or two examples of lookup queries that are very close but require two unique rules, that will help our discovery process. Thank you!

2 0
replied on June 28, 2024

Yes we would. Please see my above reply with more details.

0 0
replied on June 25, 2024

Yes, that would be great. Right now, I'm using chart.js so the client can create charts in a Laserfiche forms. I have two fields, Y-AXIS and X-AXIS. 
 

I have a hidden field where the data is filled. Ideally, I would like to be able to do this:

When X-AXIS matches with "County"
Fill ValuesTable>ID with CountyID
Fill ValuesTable>Needs with TotalNeeds

I want to be able to do this for each X-AXIS value. (County, Needs, Date, Clients)


Right now, I have separate hidden tables for each potential Y-AXIS value and then it fills the checkboxes with the corresponding value.

 


 

0 0
replied on July 2, 2024

When the lookup table API becomes available I will reach out to you and provide some links that should simplify this forms process for you!

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

Sign in to reply to this post.