QD

QuillDock

Wix CMS publish control plane

Start 14-day trial in Wix
← Back to support
mapping.reviewdraft

Fix mapping issues and unsupported fields

Problem

QuillDock cannot save your mapping or continue to preflight until the mapping meets the v1 rules.

Who this is for

Operators matching source fields from Google Sheets or Airtable to fields in a Wix CMS collection.

What you will see

  • Mapping suggestions appear only for exact-name and compatible field matches
  • Save or Continue may stay disabled
  • Validation messages explain why the mapping is incomplete or unsupported
  • Incompatible pairings stay visible inline so you can repair them before QuillDock allows save or preflight again

Likely causes

  • there is no match key
  • more than one field was marked as the match key
  • the match key is not a text or number field on both sides
  • the mapping contains unsupported target fields
  • the same source or target field is used more than once
  • only the match key is mapped and no additional field is selected

Step-by-step resolution

  1. Open Configuration / Mapping.
  2. Review any suggested mappings, but confirm them manually.
  3. Choose exactly one match key that resolves to a text or number field on both sides.
  4. Add at least one additional mapped field.
  5. Remove unsupported, duplicate, or incompatible pairings that QuillDock flags inline.
  6. Save the mapping only after every validation message clears.
  7. Move to Preflight review only after the mapping is saved cleanly.

Supported v1 target field types

QuillDock supports only the currently launch-supported target field types for the active release:

  • text
  • number
  • boolean
  • date and time
  • URL
  • single image
  • single file
  • single reference

Visible but unsupported fields can stay visible for reference, but they cannot be mapped. Deferred field classes such as multi-reference, galleries, rich content, or generic object payloads should remain explicitly unsupported until QuillDock says otherwise.

When to contact support

Contact support if the fields look compatible but QuillDock still refuses to save, if save or preflight stays disabled after you clear the visible validation messages, or if a previously valid mapping becomes invalid after source or target changes.

Related features and docs

  • Configuration / Mapping
  • Choose a Wix CMS target collection
  • Understand supported and unsupported field types at launch
  • Understand preflight blockers, warnings, and disabled publish