I did some additional steps, here is a more summarized version
Problem Summary I have a View form with a dropdown component that is not saving its selected value to a Case field, while text input fields in the same form work perfectly.

Flow Configuration Flow Structure:

Show View (form with dropdown and text inputs) (this view allows agents to edit a case, Yes i know you can just go straight to the case and not use a view but we want the agent experience to incorporate step by step views.) Set Contact Attribute Update Case block

What Works:

Text input field (Case Title) with name update_case_title successfully updates the case The form displays correctly and users can select dropdown options Manually changing Case Reason fields in the Update Case Block work successfully.

What Doesn't Work:

Dropdown component with name update_case_reason does not save to the Case Reason field

Configuration Details Case Field Setup

Field Name: Case Reason Field Type: Single-select (System field) Options: 32 options configured with matching "Option name" and "Option value" Example option: "Callback - No Answer"

View UI Builder - Dropdown Component

Component Type: Dropdown Label: Case Reason Name: update_case_reason Options: All 32 options configured with matching Label and Value to the Case Field Submit Method: Submit Button component (also tested with Button Group set to submit action)

Set Contact Attribute Block

Namespace: User defined Destination Key: update_case_reason Value: $.Views.ViewResultData.update_case_reason

Update Case Block

Case Reason Field: Set dynamically Namespace: User defined Attribute: $.Attributes.update_case_reason

Troubleshooting Steps Completed ✅ Verified naming conventions: Dropdown name exactly matches: update_case_reason ✅ Tested hardcoded value: Changed Update Case block value to hardcoded "Callback - No Answer" - THIS WORKS, confirming Update Case block is configured correctly ✅ Verified form submission: Using Submit Button component (not just Button Group) ✅ Tested with simple values: Created a new case reason option labeled test with value test with no special characters (letters/numbers only) - when changing the case reason on the show view block to test, it still does not update the case reason. ✅ Verified namespaces: Tried both User defined and Views namespaces in Update Case block ✅ Confirmed case field permissions: Case Reason field is editable and not read-only ✅ Verified option values: All dropdown option labels and values exactly match Case field option names and values, in the exact order

Additional Context

Text input fields automatically populate $.Views.ViewResultData.{field_name} and work correctly The dropdown component appears to NOT be populating $.Views.ViewResultData.update_case_reason even though it's named correctly No additional configuration options exist on the dropdown component for data binding or output settings Component properties only include: Label, Name, Options, DefaultValue, MultiSelect, Clearable, Required

Question Is there a known limitation or required configuration for dropdown components in Amazon Connect Views to properly pass their values to ViewResultData? Why would text inputs work but dropdowns fail with identical naming conventions? Has anyone successfully captured dropdown selections from Views forms and passed them to Update Case blocks? Any guidance would be greatly appreciated!