Troubleshooting, common issues and how to diagnose them

First-place-to-look for blank forms, missing fields, failed submits, and SP-side rejections.

A reference of the most common SharePoint Forms365 issues, with the first thing to check for each.

The form renders blank

First check: open the browser console. Look for errors prefixed

[forms365].

Common causes:

  • Wrong list bound, the form was authored against list A, published against list B. Re-open the form in the designer and verify the bound list under General → List.
  • SPFx package not installed in this site, visit Site Settings → Site Collection Features → SharePoint Forms365 should be activated.
  • Form definition missing, the form was deleted while still bound. Re-author or restore from history.

Fields are missing on the published form

The form may reference SP columns that have been deleted. Check the console for

[forms365] field X not found warnings.

Fix: re-open the form in the designer; deleted fields show as red placeholders. Remove them (or restore the SP column) and re-publish.

Submit fails with "InvalidFormDigest" or 403

A locked-down tenant is rejecting writes without an explicit request digest.

The runtime auto-fetches a digest on first 403 and replays, but if the retry also fails, the user lacks Contribute permission on the list. Verify SP permissions before chasing code issues.

Submit fails with a column rejection

SharePoint's error message comes back in the toast. Common ones:

  • "Required field X is missing", the form may have visibleIf hidden a required SP column. Either make the column not-required on SP, or add explicit handling in onBeforeSave to default the value.
  • "Value out of range", Number column has min/max on SP that the form isn't enforcing. Mirror the bounds in the field's properties.
  • "Cannot save with invalid value", Choice column doesn't accept the submitted value (probably because a fill-in choice was disabled mid-edit).

Console shows "Failed to fetch dynamically imported module"

Vite HMR hiccup during dev; not a production issue. Hard-reload the page.

Dev hot-reload doesn't update the form

You're running gulp serve-deprecated, but the form bundle isn't swapping. First-time setup: visit https://localhost:4321/ in your browser and accept the self-signed cert. Then verify the SP debug URL has

debugManifestsFile=https://localhost:4321/temp/build/manifests.js.

"I fixed it but SharePoint still shows the old behaviour"

Probably stale-cache. SP's CDN can serve the old JS bundle for ~5 minutes.

For dev: hard-refresh with cache disabled (F12 → Network → Disable cache). For production: every shipped .sppkg gets a fresh solution version, bumping the version is what invalidates the CDN.

Where the logs live

Browser console errors are prefixed [forms365]. Backend errors land in the production logger at https://apilogger.sharepointpro.com.au under project aiforms365-internal-backend, searchable via the admin tools.