I am using desktop version 23.1.10.591 on Windows 11 64 bit. I have updated to the latest version. This latest version (and earlier versions) allow the deletion of Classic Custom Fields when data exists in these Custom Fields

This was an issue with both classic and new custom fields. Anyway, the latest version (23.1.18) is fixing this. Passing empty value in batch update will remove the custom field from the object rather then setting it empty.

Deleted and Unused Classic Custom Fields remain in transactions

Ealfardan January 11, 2023, 9:06pm 9

There’s been a recent bug for exactly that that’s been solved in version 23.1.2

What version are you running?

Topic		Replies	Views
Cannot fully upgrade or delete Classic Custom Fields bugs	4	113	May 21, 2025
Deleted Classic Custom Fields still show in Batch Update file	1	200	January 10, 2023
Batch update to empty custom field values does nothing	10	329	January 18, 2023
Custom fields can be deleted after use	2	1080	December 1, 2017
Custom Fields Disappeared	6	362	January 18, 2023

Deleted and Unused Classic Custom Fields remain in transactions

Related topics