From 96718d173cf81b6e1d7b318699c3850c369bb783 Mon Sep 17 00:00:00 2001 From: "vamsi.balaga" Date: Tue, 27 Oct 2026 18:37:07 +0530 Subject: [PATCH] fix: leave Assigned by out of the Assign form field_5 is a select in the builder and the runtime rejects any value not in its options, so sending employee names failed with "Assigned by must be one of the listed options". Drop it from the form, as Reassign already does for field_11, until the builder field is changed to text. Co-Authored-By: Claude Opus 5.5 --- src/api/assets.js | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/api/assets.js b/src/api/assets.js index 30bd996..abdda7a 100644 --- a/src/api/assets.js +++ b/src/api/assets.js @@ -229,9 +229,10 @@ export const ASSET_ASSIGN_ACTIVITY_ID = 'd18815a4-4e74-480d-a943-67dce894412f' /** Fields the user fills in. */ export const ASSET_ASSIGN_FIELDS = [ { id: 'field_1', label: 'Assigned date', type: 'date' }, - // The builder has no options for Assigned by, so the form offers the active - // employees' names (`employeeOptions`, filled in by the dialog). - { id: 'field_5', label: 'Assigned by', type: 'select', options: [], employeeOptions: true }, + // Assigned by (field_5) is left out of the form on purpose: it is a select in + // the builder and the runtime rejects any value not in its options ("Assigned + // by must be one of the listed options"), so employee names can't go there. + // Add it back, with `employeeOptions: true`, once the builder field is text. { id: 'field_6', label: 'Remarks', type: 'longtext' }, { id: 'field_21',