Add full name binding to user metadata for option pickers

[ConorWebb96]

Description

Adds a new fullName user field for picker bindings and user metadata outputs. It is computed from firstName + lastName (with fallback to single name, then email), persisted for new/updated metadata, and also computed at read time for older records.

Additionally

• Marks fullName as a non-editable system field in the Builder users table
• Adds tests for sync, fallback, and binding behaviour.

Addresses

• Add full name binding to user metadata for option pickers #18197

Screenshots

New user binding

Custom option picker that points at the user table

Table User column copied value

{"_id":"us_4d8ef972996a4085af8ebc3827fd8b50","primaryDisplay":"test@test.com","email":"test@test.com","firstName":"Test","lastName":"Test","fullName":"Test Test"}

Launchcontrol

This change makes Budibase consistently show people by full name in user pickers. Even older users now get a full name automatically, so you don’t have to edit and save profiles to make names appear correctly.

[cubic-dev-ai]

No issues found across 14 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

[cubic-dev-ai]

1 issue found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/server/src/api/routes/tests/viewV2.spec.ts">

<violation number="1" location="packages/server/src/api/routes/tests/viewV2.spec.ts:3758">
P2: This assertion no longer verifies the new `fullName` field, so the test can pass even if `viewV2.search` stops enriching squashed user references with the value this PR adds.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.}

[deanhannigan]

I had a good run through this and it seems pretty solid 👍. I don't really understand the need to persist a fullName element to the db at all considering we have the same information already at hand.

• BUG - Column default not working.
  • Add a column. Set the default to the {{ Current User.fullName }}.
  • Create a row and the default won't load.
  • Setting {{ Current User.firstName }} does work, along with the other user bindings

[deanhannigan]

LGTM! All issues resolved 🚀

Changes completed