Closed grasela closed 3 years ago
I'll update the wording to indicate the conflict is with an archived model.
I've altered the constraint - you can now create a new field with the alias of an archived field.
foo
foo
foo
Original functionality - the reported error would show.
New functionality - a new field called foo
will be created.
The same applies to models and aliases. If you try to restore a deleted model with the same alias an error will show.
I have temporarily disabled the ability to view and restore archived models while the UI flow is worked on.
This will be returned shortly.
'Model aliases must be unique' That's confusing because I tried to find the model of the same alias and couldn't find it. Almost lost my patience .. before I realised the archived ones are counted for this too. This needs better communication