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.

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.

@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.

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.

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.

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?

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.

Did you also test if it is a Dynamic field?

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.

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.

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.