Issue-716 - check for duplicate system label #717
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create a new warning in studio for duplicate system labels when creating a new field.
Description
The same system label could potentially be used for more than one field. When creating a new field with a used system label, the new display label overwrites the old one, changing the display label for both fields.
A warning now appears on the form if the system label already exists in the module when attempting to create a new field. The field will not be created in this scenario.
Issue here: #716
Motivation and Context
Two fields had the same system label. One field's display label was changed to the newly create one as a result.
How To Test This
See #716
Types of changes
Final checklist