QD

QuillDock

Wix CMS publish control plane

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

Understand supported and unsupported field types at launch

Problem

You want to know whether a field can be mapped, preflighted, and published in the current verified QuillDock launch surface.

Who this is for

Operators setting up or reviewing a QuillDock publish flow from Google Sheets or Airtable into one Wix CMS collection.

Supported field types at launch

QuillDock supports these target field classes in the current launch surface:

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

Important limits inside the supported surface

  • Single image means one usable image URL or one attachment per row.
  • Single file means one usable file URL or one attachment per row.
  • Single reference means one resolvable reference per row to an item that already exists in the referenced Wix collection.
  • QuillDock does not create referenced items for you.

Deferred field types and workflows

QuillDock does not support these at launch:

  • galleries or multi-asset media writes
  • multi-reference fields
  • self-reference or graph-style reference automation
  • rich content or block content
  • generic object or array payload syncing
  • 2-way sync
  • cross-collection orchestration
  • custom transforms

What to do when a field is unsupported

  1. Leave the unsupported field unmapped.
  2. Continue with the supported fields you do need for this publish flow.
  3. Rerun preflight after you update the mapping.
  4. Publish only from a fresh passing trusted snapshot.

What to do when a supported field is still blocked

  • For image or file fields, make sure each row has only one usable asset value.
  • For reference fields, make sure each row has only one reference value and that the referenced Wix item already exists.
  • Rerun preflight after you fix the source data or mapping.

When to contact support

Contact support if a field looks like it belongs to the supported list above, but QuillDock still keeps it blocked after you rerun preflight from a fresh saved mapping.

Related features and docs

  • Configuration / Mapping
  • Preflight
  • Fix mapping issues and unsupported fields
  • Understand preflight blockers, warnings, and disabled publish