A unified data governance solution that helps manage, protect, and discover data across your organization
Classic Microsoft Purview glossary import only supports the column types and behaviors defined in the selected term template. For numeric custom attributes (such as Integer), an empty value in the CSV is interpreted as the default for that data type, which results in 0 being stored rather than a blank.
The import pipeline does not expose an option to change this behavior or to treat empty numeric cells as NULL/blank. The only supported way to have a truly blank value is to use an attribute type that allows empty text (for example, a Text custom attribute) instead of an Integer, or to avoid including that column in the CSV for terms where it should remain unset.
If the attribute must remain numeric for other terms, the behavior cannot be changed via CSV import in the classic glossary; post‑import manual edits or a different attribute design (for example, a Text attribute that is interpreted as a number downstream) are required.
References: