Using the Notes Field for AI Automation

I have been doing some research on this as well but don’t believe this is possible through standard behavior, maybe with a customization project it’s possible. 

From my understanding, even though you can display the Note text field on the form directly in modern UI and edit the note text from the UI, but it is still not being treated like a standard input field that the AI prompts can target directly. 

And according to the AI Agent on the partner portal, this is due to note text being managed through the notes dialog, and not like other input fields on the form. 

Yes — Notes is a better place than a UDF for a validation result, but it usually does not appear in the Input Data Field / Output Data Field picker. That does not always mean it is unsupported. Notes is not a regular form control; it is typically NoteText on the current record.

When a field is missing from those dialogs, use Element Properties on the source form and put the exact ViewName.DataField in the prompt. For output, the help format is @((ViewName.DataField)).

Example I tested conceptually for an AP bill:

text

## Context Instructions
You are an accounting assistant writing a short internal note for an AP bill.

## Instructions with Input Data
Vendor: ((Document.VendorID))
Amount: ((Document.CuryDocBal))
Invoice Date: ((Document.InvoiceDate))
Invoice Number: ((Document.InvoiceNbr))

## Output Data Field
@((Document.NoteText))

Two details that matter:

• Use NoteText, not Note.
• Confirm the view name with Element Properties. On Bills and Adjustments it is often Document, not APInvoice.

On 26R2 preview, in a recent AI class, this kind of thing worked with a plain instruction and no special formatting, for example:

Find the number of invoices for the customer and their status and add the result to the Customer Note.

On 26R1, AI Automation is more limited. You still cannot update document detail lines there; that was added in 26R2 (GA planned for October 2026). I would not be surprised if writing to Notes follows the same split: possible in 26R2, unreliable or unavailable in 26R1 even with the correct placeholder.

So in practice:

• 26R1: keep the UDF if Notes does not update.
• 26R2: try @((…NoteText)), or a plain “write the result to the record note” instruction, then test on one record.

If it still does not write, check Trace to see whether NoteText is actually in the payload sent to the LLM.