Map Editor Forms vs. MDC Portal Forms: What’s the Difference?

There are two places to create a form for data collection: the Forms Manager in Map Editor, and the MDC Portal. People often ask which one is “better” — but the truth is the forms themselves aren’t all that different. What differs is the context each one is created in, and a couple of specific capabilities tied to that context.

What’s the same

• Both let you build a form from the same set of form items (text, numeric, date/time, select, radio, checkbox, signature, photos, QR/barcode, etc.).
• Both forms can be reused across multiple layers and multiple maps once created.
• Both support the same quality-control options — required fields, unique values, dependencies, grouping, translations.

Where they differ

1. Project vs. form

• Creating a form in MDC Portal means you’re creating an entire project in one step: the form, its underlying table, and the map it feeds into are all generated together, automatically linked to each other.
• Creating a form in Map Editor’s Forms Manager creates just the form. It stays independent until you connect it to a layer yourself — which means the layer has to already exist (or be created alongside it).

2. Editing existing data

• An Editor form can be built from an existing layer: point it at the layer and it auto-generates matching form fields. It also doesn’t have to cover every attribute column — you can leave some fields out of the form entirely, or add extra layer columns visible only to you in Map Editor.
• An MDC Portal project is built for new data collection, not for wrapping a form around data you already have.

3. JSON mode and automations

• Map Editor forms can be switched to a JSON view, letting you edit the form’s underlying structure directly. This unlocks things that aren’t exposed in the UI at all — more advanced automations, bulk edits to select-list options, and faster repetitive setup.
• MDC Portal forms don’t have a JSON mode — you’re working within the UI’s options only.

4. Autofill

• In MDC Portal, Autofill can only pull data from the same layer/project you’re currently collecting into — it fills a field from the nearest previously-collected point.
• In Map Editor, Autofill can pull from any layer on the map, not just the one you’re collecting to. You enter the source layer’s ID and the field(s) to fetch from, which also means it can be set up via JSON for larger or more repetitive setups.

5. Where you can edit the form afterward

• A form created in MDC Portal has its form-to-layer connection locked in — the columns can’t be edited through Map Editor afterward. To change it, you go back to MDC Portal.
• A form created in Map Editor stays editable there, and you explicitly connect (or reconnect) it to a layer’s columns yourself.

Which one should you use?

Since the forms themselves aren’t fundamentally different, the real decision is about your workflow:

If you’re unsure or need any help getting started, you can always reach out to our Support team (premium-support@giscloud.com)!