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

Discussion

Discussion

Smart Fields overriding our prompts with the field's display name

Laserfiche AI
Updated one day ago
posted on December 23, 2025

I did not expect the display name of a field to override the prompt when using Smart Fields.

As an example to demonstrate how the display name effects the prompt we prompted to get a full name (last, first, middle initial) but when we change the display name of the field to "First 4 letters of the last name" without modifying the prompt it overrides the prompt as the result is the first 4 letters of the last name instead.

1 0
replied two days ago

The display name is used in the prompt as additional context for data extraction.  In your case the display name, which includes "First 4 letters", will impact the extraction since there is a conflict between what the display name is instructing and the description.

When there is a conflict of this nature, even if the conflict was inside the description (providing a description that has multiple conflicting objectives), the LLM will try to resolve and is not deterministic.

You can add in your description some text to disregard any instructions in the name if this behavior is not desired.  For example, something like the following:

Get a full name (last, first, middle initial).   Disregard any instructions in the field name and extract the full name as specified.

0 0
View 8 previous replies
replied two days ago

Is it just the display name that adds context, or is the field name used as well? Also, the documentation makes no mention of anything but the Description being used for the extraction so that should be updated.

2 0
replied two days ago

We created the conflict on purpose to confirm the field display name was being included in the prompt. Can we make it a checkbox instead, this is counter intuitive. The display name was meant to be the name of the field displayed to the user but not expected to interact with a prompt for the data we want to capture.

0 0
replied two days ago

@Pieter,

We use several bits of information from the field definition to aid in the data extraction:

  • Display Name
  • Description
  • Type
  • Length
  • Allow multiple values

 

Although, the "Description" is the main part of the instructions for data extraction.  We will review the documentation and update.

 

@Chad,

Having the ability to disable part of the information being used for data extraction is a feature request that would need to be evaluated.  I would recommend making a request using the "Feedback" form in Laserfiche to start the process.

0 0
replied two days ago

Thanks, Shawn-

Yeah, I noticed that type seemed to play into it. I had a text field with formatting meant to accept only dollar amounts because copy/paste from the document didn't work with commas if going into a numeric field. But after moving to AI, switching that back to the numeric field got a lot better results.

1 0
replied one day ago

I think using the type, length, and other features makes sense. Just modifying our prompt for what we are asking for with text from the display name is counter intuitive to myself and our clients. The prompt defines what data we want to extract, the display name defines what title to show on the field in the repository.

0 0
replied one day ago

Not to take this conversation down a different path, but the list of information used brought up another question. If the field is a list, is Laserfiche AI smart enough to only look for values present in the list? Also, what if it is a dynamic field?

1 0
replied one day ago

Yes I believe so, I did some testing to try this concept out and it appears to only work with the values in the list finding the closest match.

0 0
replied one day ago

Did you also test if it is a Dynamic field?

0 0
replied one day ago

I'm doing this with invoices where the vendor is a dynamic field and no, it's not matching against that list. Although it's set up as a text field, not a list, so maybe that affects it.

0 0
replied one day ago

I have not yet, but that is only a different way to populate the drop down, I would hope it would work the same unless there was a disconnect in the technology.

0 0
replied one day ago

Pieter, that's exactly what I would be doing with it too, but our vendor field is configured as a list, which is why I'm curious.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...