You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you update the key and description fields for a schema, but leave the title field as "field0", multiple Fields with the title of "field0" are created.
I don't really know the impact of this happening, but since I suspect it may cause something to go wrong somewhere, I manually updated all the titles to match the key. Since it can be managed manually I would say this is Low priority.
Step to reproduce
Steps to reproduce the behavior:
Create a new schema
Add a field to the new schema
In Advanced, update the key and description to "...new value...". Do not update the Title (stays as field0)
Add another field to the schema
Expected behavior
I would expect the Title value to increment or be forced to update when the key is updated. I suspect that the Title is created as field0 because it feeds off the key when the item is created, but since it doesn't update when the key is updated, you get multiple fields with the same title.
Screenshots
The text was updated successfully, but these errors were encountered:
Problem description
When you update the key and description fields for a schema, but leave the title field as "field0", multiple Fields with the title of "field0" are created.
I don't really know the impact of this happening, but since I suspect it may cause something to go wrong somewhere, I manually updated all the titles to match the key. Since it can be managed manually I would say this is Low priority.
Step to reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the Title value to increment or be forced to update when the key is updated. I suspect that the Title is created as field0 because it feeds off the key when the item is created, but since it doesn't update when the key is updated, you get multiple fields with the same title.
Screenshots
The text was updated successfully, but these errors were encountered: