I see from BuiltInDocumentPropertiesDictionary that System.String values cannot be null or System.String.Empty, meaning that these properties cannot be set to an empty string.
However, the result is that the generated documents are missing property elements. Compare these docProps/core.xml between one from Word (new document):
<dc:title/>
<dc:subject/>
<dc:creator>me</dc:creator>
<cp:keywords/>
<dc:description/>
<cp:lastModifiedBy>me</cp:lastModifiedBy>
and one generated by Gembox:
<dc:title>myfile</dc:title>
<dc:creator>me</dc:creator>
<cp:lastModifiedBy>me</cp:lastModifiedBy>
The result is that DOCPROPERTY fields in Word behave differently. For instance, the field {DOCPROPERTY Subject} in my Word document disappears, whereas in the Gembox document it is replaced by Error! Unknown document property name.
Is it possible to permit empty strings or, in some other way, allow these empty properties in the doc props?
Hi Craig,
Please try again with this NuGet package:
Install-Package GemBox.Document -Version 2026.10.119
Note that this is a hidden (unlisted) version. To install it, you’ll need to run the above command on the NuGet Package Manager Console (Tools → NuGet Package Manager → Package Manager Console).
Does this solve your issue?
Regards,
Mario
Hi Mario,
This solves some of the problem. I can now set the built-in properties, and regardless they are appearing in the core.xml.
However the doc.GetPaginator(new PaginatorOptions() { UpdateFields = true }); is not updating the DOCPROPERTY Subject.
I have two consecutive fields in the document (in the header) as shown in the picture below. I’m doing documentProperties.BuiltIn[BuiltInDocumentProperty.Subject] = ""; but the output still says Error! Unknown document property name. If I right-click on the field and Update Field then I get the expected behaviour which is a blank field.
Thanks 
Hi Craig,
DOCPROPERTY fields are updated with Field.Update() method.
Nevertheless, please try again with this NuGet package:
Install-Package GemBox.Document -Version 2026.10.120
Note that this is a hidden (unlisted) version. To install it, you’ll need to run the above command on the NuGet Package Manager Console (Tools → NuGet Package Manager → Package Manager Console).
Does this solve your issue?
Regards,
Mario
Mario,
This is looking great.
My apologies on the field rules. I was making an assumption from the title behaviour for the subject.
Thank you once again for such quick feedback - you and your team do great work 