Problem

When creating a workspace from a template with dynamic parameter ordering, parameter values are not displaying correctly when the order changes. This occurs when a parameter'sorder value depends on another parameter's value.

Example scenario:

data"coder_parameter""reorder" {name="reorder"type="bool"default=falseorder=1}data"coder_parameter""cpu" {order=data.coder_parameter.reorder.value?0:2name="cpu"type="number"default=4}

When the user togglesreorder fromfalse totrue, thecpu parameter moves from position 2 to position 0, but its value gets mixed up with thereorder parameter's value.

Root Cause

The issue was inCreateWorkspacePageViewExperimental.tsx where parameters were rendered using array indices instead of parameter names:

// Problematic codeconstparameterField=`rich_parameter_values.${index}`;constformValue=form.values?.rich_parameter_values?.[index]?.value||"";

When parameters are reordered:

1. Theparameters array order changes based on the neworder values
2. Theform.values.rich_parameter_values array maintains the original order
3. Array index-based lookup causes values to be mismatched

Solution

Implemented name-based lookup to ensure parameter values stay with their correct parameters:

// Find parameter value by name instead of indexconstcurrentParameterValueIndex=form.values.rich_parameter_values?.findIndex((p)=>p.name===parameter.name)??-1;// Use the found index for form field mappingconstparameterFieldIndex=currentParameterValueIndex!==-1 ?currentParameterValueIndex :index;constparameterField=`rich_parameter_values.${parameterFieldIndex}`;// Get form value by name to ensure correct mappingconstformValue=currentParameterValueIndex!==-1   ?form.values?.rich_parameter_values?.[currentParameterValueIndex]?.value||""  :"";

Testing

• ✅ Created test script that validates the fix works correctly
• ✅ Tested with the provided template showing dynamic parameter ordering
• ✅ Verified parameter values persist correctly during reordering
• ✅ Confirmed no TypeScript compilation issues

Impact

This fix ensures that users can reliably use dynamic parameter ordering in their templates without losing parameter values when the order changes. This is particularly important for templates that use conditional parameter visibility and ordering based on user selections.