Disable already mapped fields on mapping add form

Created on 28 July 2023, over 1 year ago
Updated 18 August 2023, about 1 year ago

Problem/Motivation

When new adding mapping you cannot easily see which destination fields are already mapped. And it is also not possible to map to the same destination field twice, because that results into the following error if you try that:

A mapping with the destination key created already exists.

Steps to reproduce

  • Add mapping to a destination field.
  • Try to add mapping to the same destination field again.

Proposed resolution

Therefore I think we should disable already mapped destination fields from the mapping selector:


In the example above "changed" and "created" can no longer be chosen, because these are already mapped.

Remaining tasks

User interface changes

API changes

Data model changes

Code changes will follow.

Feature request
Status

Fixed

Version

1.0

Component

User interface

Created by

🇳🇱Netherlands megachriz

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024