Discussion

Unable to use multiple DB.Null in a Forms Lookup as paramater

Forms

Updated April 8

posted on November 20, 2024

Hello,

I wanted to report a bug we are having where we are unable to add more than one _(DB.Null) as a parameter to a Stored Procedure or Table lookup. You can save it once, but when coming back into the Lookup Rules on the modern designer, the system removes _(DB.Null) from the list.

If you fully delete the lookup rule and recreate, it will save and work, it is just anytime you open the page for any sort of adjustments you will have to fully recreate your mappings.

0 0

Comments 4
Follow-Ups 0

replied on April 8

Hi, this issue has been fixed on Forms 12 Spring 2025 Release: allow configuring multiple DB.NULL fields for use lines. (BugID: 521096)

You can see other changes from: Laserfiche 12 Release Information

Get the latest Laserfiche Forms 12 package from: Laserfiche 12 - Downloads

0 0

replied on November 20, 2024

Hello,

Correct, if you do not do any Lookup Rule maintenance it works fine.

0 0

replied on November 20, 2024

Not great, but at least you are able to get it working. I have prioritized it for our next release in spring

0 0

replied on November 20, 2024

Good morning, I was able to reproduce this issue in Laserfiche 12. I filed a bug to fix this for the next release #555381

Can you confirm the lookup works as long as you dont touch it again when previewing or using the form?

0 0

You are not allowed to follow up in this post.

Discussion

Discussion

Unable to use multiple DB.Null in a Forms Lookup as paramater

Comments 4

Follow-Ups 0

Sign in to reply to this post.