Can't create a metadata field with the same external id of the one that was deleted
Reproduce steps:
- Create a metadata field with the external id `test`.
- Delete it
- Create a new metadata field with the external id `test` -> it says the `test` already exist.
-
Hi Steven,
Thanks for contacting us.
That's currently the expected behaviour - 'deleting' a metadata field deactivates it, makes it invalid for use in future API calls and hides it from view, but the record remains in your account's database.You can create a new field with the same "label" value and a different or automatically-set external_id value and it appear the same as the previously-removed field in the UI
Regards,
Stephen
0 -
Hi Stephen,
If you keep the record in my account's database, why isn't there an option for me to restore it? we can't rely on the `label` as it doesn't return in the resources' `metadata` key.
I accidentally created a metadata field with a desired `external_id` but with a wrong type -> I couldn't update the type (like from `enum` to `set`) -> I got to delete the field to add it again -> I couldn't create the field with the original `external_id`.
Regards,
Steven.
0 -
Hi Steven,
In general, it's not intended that deleted fields can be restored or their external_id values re-used - the external_id field is intended for internal/backend use and we recommend these are left with automatic values set, and that you use the 'label' to show the details of those fields to your application users
If there's a specific field you'd like us to try and recover, or permanently delete, please open a support request with the details. It may be possible via our backend team, assuming in the case of deletion that the field wasn't already used by existing assets.
Thanks,.
Stephen
0
Post is closed for comments.
Comments
3 comments