SharePoint Document Issues

Fix SharePoint List Form Error: SPFieldChoice Cannot Be Cast to SPFieldNumber

Maira Mehtab Sep 28, 2026 869 views

Question details

The user cannot edit or submit an InfoPath-based SharePoint list form due to a field type mismatch error.

Product: SharePoint / InfoPath
Device & OS: not provided
Scenario: Editing or submitting a custom InfoPath list form connected to a SharePoint list.
Observed behavior: The form fails to submit, displaying an error message stating that SPFieldChoice cannot be cast to SPFieldNumber, despite the columns appearing to match.

Before you start

Verify that you have Site Owner or Designer permissions for the SharePoint list and the corresponding InfoPath form before attempting to modify data connections or field types.

Solution 1Recommended

Verify and Sync SharePoint and InfoPath Field Types

Check for hidden discrepancies between the SharePoint list column settings and the InfoPath form data schema.

This error typically occurs when InfoPath sends a choice or text value to a SharePoint column that is strictly configured as a Number (SPFieldNumber). Even if they appear to match, the underlying data schema might be out of sync.

Check SharePoint List Settings

Navigate to your SharePoint list, click the Settings (gear) icon, and select 'List settings'.

Review the Target Column

Locate the problematic column in the Columns section. Ensure its type is explicitly set to what InfoPath expects (either 'Number' or 'Choice').

Refresh InfoPath Data Connections

Open your customized list form in InfoPath Designer. Go to the Data tab and click 'Refresh Data Fields' to update the connection schema from SharePoint.

Republish the Form

Once the field types are perfectly aligned, click 'Quick Publish' to republish the InfoPath form to the SharePoint list.

Caution on Changing Field Types: Changing an existing SharePoint column from 'Choice' to 'Number' may result in data loss if existing records contain non-numeric text.

Solution 2

Seek Specialized Assistance on Microsoft Q&A

Since this involves advanced InfoPath forms and SharePoint development, consult the Microsoft developer community for tailored assistance.

Free Microsoft Office alternative

Looking for a simpler way to manage your documents?

While resolving complex SharePoint and InfoPath form errors often requires specialized IT development, everyday document creation shouldn't be difficult. WPS Office provides a free, lightweight, and incredibly powerful alternative to Microsoft Office for your Word, Excel, and PDF needs.

Seamlessly compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight design that loads quickly without draining system resources.Intuitive, familiar interface that requires zero learning curve.Built-in advanced PDF editing, splitting, and merging tools for free.

microsoft office alternative - wps office

Frequently Asked Questions

Why does SharePoint say SPFieldChoice cannot be cast to SPFieldNumber?

This casting error happens when an InfoPath form attempts to submit data formatted as a choice (text/string) into a SharePoint list column that is strictly configured to accept only numerical values.

Can I change a SharePoint column type after creating it?

Yes, you can modify column types via 'List Settings'. However, changing incompatible types (like Text to Number) might break connected InfoPath forms or cause existing list data to be wiped out.

Is InfoPath still supported by Microsoft?

InfoPath 2013 is the final version of the product and is in extended support until 2026. Microsoft currently recommends migrating custom SharePoint list forms to Power Apps.

Document & File Issues