search

performant-software / core-data-cloud

Core Data. In the Cloud.
0 stars 1 forks source link

Unable to save new order values in user-defined fields #171

Open absempere opened 6 months ago

absempere commented 6 months ago

I am trying to reorder user-defined fields under Person/Fields in the Criadas model, and changes to the order number aren’t saving.

Editing and saving the field record appears to work. The order number updates:

Screenshot 2024-03-27 at 10 34 43 AM

However, saving the model appears to reset the order values to the order in which the fields were added:

Screenshot 2024-03-27 at 10 35 31 AM
absempere commented 6 months ago

@dleadbetter New twist on this bug: I deleted all of the Fields to start the data model over. When I tried to reorder "Age" and "Biography" and saved the model, the order numbers were changed from 1 and 2 to 9 and 10. It appears to be counting the deleted fields and adding these new fields after those and still isn't allowing me to reorder the fields.

Screenshot 2024-04-04 at 11 51 22 AM
dleadbetter commented 6 months ago

This looks to be a bug. A workaround would be to remove the field an re-add it, but only if no data has been entered.

absempere commented 6 months ago

@dleadbetter Can I delete the data and then remove & add? I have test data in some of the fields I'm trying to modify... we were experimenting with the model and whether certain things should be fields or taxonomies, so I've been moving things around as we work through it.

dleadbetter commented 6 months ago

@dleadbetter Can I delete the data and then remove & add? I have test data in some of the fields I'm trying to modify... we were experimenting with the model and whether certain things should be fields or taxonomies, so I've been moving things around as we work through it.

@absempere - No need to remove the data if you don't need to preserve it. I was just trying to communicate that deleting the field would result in losing the data.

NickLaiacona commented 3 months ago

I encountered this bug today as well, trying to reorder fields in the NBU Person records.