Release 2.5.23

Issues fixed

Fixed: migration export could fail for items without persisted XML
The migration export pipeline could fail with a database error when an item had no source or export XML to persist — for example when the XML was intentionally not stored, or when it could not be parsed. Export now skips storing XML in that case instead of sending an empty value to the database, so the run completes and the affected item is recorded with its parse error. This brings the 2.5 and 2.6 release lines in line with the equivalent 2.4.32 fix for the same class of failure.

Translation valuesets with null in numeric columns now upload, download and load correctly in the Portal
Translation valuesets containing null values in numeric columns did not round-trip correctly. After uploading a valueset with [null] in a numeric column, downloading it returned an empty cell instead of [null], and loading the valueset into Staging could fail with a conversion error ("the given value '' of type String … cannot be converted to type decimal").

Empty text in non-text columns is now consistently stored and treated as null, so null numeric values upload, download and load into Staging as expected. Rows previously corrupted by this issue are recovered automatically on load.