When I try to Upgrade a Classic Custom Field, Manager successfully creates a CustomField2 however it fails to delete the old custom field.
I tried to remove all values from these classic custom field and then Batch Delete and didn’t work. I also tried deleting them individually and no luck either.
I have gone through this process before, and I can vaguely remember the old custom field being removed, that’s why I’m submitting a bug report for this.
Edit: I later inactivated those fields and now they’re completely gone.
This appears to be an undocumented feature to allow users to review the changes before deleting the obsolete fields.
I have faced a similar issue while updating fields in my setup. Even after clearing values, the classic custom field wouldn’t delete. It might be a backend bug—I’d recommend reporting it with detailed steps, or trying a full data export/import workaround if it’s urgent.
I think I am experiencing a related issue, specifically with the data Manager is sending via the Relay service. We have a custom field for VAT number:
We had the same custom field under the legacy custom fields (now as Classic Custom Fields under Obsolete Features). However, at some point I deleted all the Classic Custom Fields and created corresponding new ones. We now have no Classic Custom Fields:
We use the Relay service to “fiscalise” our invoices. This service (developed by a third party locally) is giving us an error for one of our invoices, saying the VAT number is incorrect. I have used Manager’s Relay test service to examine the data being sent, and I see that although we have updated the customer’s VAT number (visible under “CustomFields2”), the old one is also being sent under “CustomFields”. The field ID is the same in both cases (0cb0485c-8ded-405e-aaec-71d7ff08dedf).
We need to stop the old custom field data from being sent in the Relay, but since the old custom field has been deleted and is no longer visible in the Customer edit form there doesn’t appear to be a way for us to do this.
I think this is a bug, in my case as well, some of the fields transitioned just fine but for the rest of the fields, I’m left with blank entries in Classic Custom Fields.
If I delete these blank entries, the corresponding Custom Fields2 get deleted as well.
