GroupDocs.Metadata for .NET - Cannot Read Custom Properties

GroupDocs.Metadata Product Family
1

I built an app about 2 years ago that uses the Metadata product for .NET and was working fine. Within the last month however, the metadata for custom properties stopped returning. The function below loops through the properties and reads the “Name” for each. But, the custom properties are no longer in that list. No changes have been made to the function since it was built and various documents have been tried, including the original files used for testing.

Document Properties.png (7.5 KB)

Here is how I’m reading the metadata from a media stream.

using (Metadata metadata = new Metadata(ms))
{
  // try and get metadata
  try
  {
    // look for custom props
    var metaProps = metadata.FindProperties(p => !p.Tags.Contains(Tags.Document.BuiltIn));
    // loop through the properties 
    foreach (var metaProp in metaProps)
    {
      if (protectionTypes.Contains(metaProp.Name.ToLower()))
      {
        // do something here if a match is found
      }
    }
  }
}

Attached are the properties in the word doc

Document Properties.png (7.5 KB)

2

I tested this further and while using an old license from last year, the custom properties were returned. Only when I then updated the license to the 2025 subscription did the custom properties stop appearing.

Attached is what the custom property should look like.
image.png (5.8 KB)

3

@zshane

Could you please share the version of the GroupDocs.Metadata API that you are using in the application? Are you saying that the same application works when you use the old license but stops working (as expected) when you use the latest license file, even though the API version remains the same?
It would be great if you can share a sample console application along-with the problematic file to reproduce the issue at our end.

4

I’m using GroupDoc.Metadata for NET 21.8.0.

And yes, the only thing I changed is the license file. The app is able to get the license, fetch the metadata properties, but the custom properties aren’t returned.

So to reproduce, you could try a 2025 license file and use that version I suppose? My app is built with Azure Functions and SFPx. I don’t have a console app that I can share unfortunately.

Here is the license file details:

<?xml version="1.0"?>
<License>
  <Data>
    <LicensedTo>[X]</LicensedTo>
    <EmailTo>[X]</EmailTo>
    <LicenseType>Developer OEM</LicenseType>
    <LicenseNote>1 Developer And Unlimited Deployment Locations</LicenseNote>
    <OrderID>[X]</OrderID>
    <UserID>[X]</UserID>
    <OEM>This is a redistributable license</OEM>
    <Products>
      <Product>GroupDocs.Metadata for .NET</Product>
    </Products>
    <EditionType>Professional</EditionType>
    <SerialNumber>[X]</SerialNumber>
    <SubscriptionExpiry>20251221</SubscriptionExpiry>
    <LicenseVersion>3.0</LicenseVersion>
    <LicenseInstructions>https://purchase.groupdocs.com/policies/use-license</LicenseInstructions>
  </Data>
  <Signature>[X]</Signature>
</License>
1 Like
6

@zshane
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): METADATANET-4112

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

7

Hi, @zshane !

Thank you for your request!
Can you please explain why do you have to use old 21.8 version instead of the latest one with the license you have?
If you have updated license you are free to update version within the license period.

So far we can not reproduce the same issue with few sample docx, png files.
Also, I have few concerns if the new license was applied correctly to the old 21.8 version. That also can impact on functionality.

I guess the latest 24.12 has not any breaking changes with public API comparing with 21.8 so I assume you can use the latest easily.

Please share your thoughts!