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

Question

Question

Dropdown shows value instead of label in Action History (intermittent, lookup-driven fields)

asked on March 25

I’m running into an inconsistent issue with dropdown fields in Laserfiche Forms and wanted to see if anyone else has experienced this or identified the root cause.

 

Scenario

  • Dropdown fields are configured with labels (display text) and values (stored value)
  • Values are being populated via lookup rules
  • Some of these dropdowns are inside collections (though the issue may not be limited to collections)

 

Issue

When reviewing the Action History → Submitted Form (initial step):

  • Some dropdown fields display the underlying value instead of the user-friendly label
  • This happens intermittently
  • Within the same submission:
    • Some rows in a collection display correctly (label)
    • Others show only the raw value

 

Important Behavior

  • As the form progresses through workflow steps, the issue sometimes seems to resolve itself
  • Later steps in Action History often display the correct label
  • The problem is most noticeable on the initial submitted form snapshot

 

Observations / Hypothesis

  • It feels like a timing or lookup resolution issue
  • Possibly:
    • Lookup not fully resolving before the form snapshot is stored
    • Partial population of collection rows at time of submission
  • However:
    • Not all rows are affected
    • Not all submissions are affected
    • Makes it difficult to isolate

 

Questions

  1. Has anyone seen dropdowns display values instead of labels in Action History?
  2. Is there a known issue with:
    • Lookups + collections?
    • Timing of field population before submission snapshot?

 

Goal

Ensure that Action History consistently shows the label (display value) so users can easily interpret past submissions.

0 0

Replies

replied on March 25 • Show version history

This is close to needing a support ticket. I do need more information though.

  1. Which form designer?
  2. What kind of lookup source? Lookup table? API?
  3. How large is the result of the lookup? I.e., how many rows?
  4. Is there any JS on the form?
  5. Any formulas/field rules?

 

We have (and still are) spending substantial time on lookup rule behavior in the bp form designer. This issue hasn't come up in any of our testing so far. I only ran a couple tests but cannot reproduce it.

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

Sign in to reply to this post.