Skip to main content
Solved

Reading Utility Network Data via ArcSDE - Resolved attributes unexposed

  • November 28, 2025
  • 3 replies
  • 137 views

ebygomm
Influencer
Forum|alt.badge.img+46

Reading Utility Network Data in a FeatureReader with an SDE connection with resolve domains and resolve subtypes ticked.

Domains can be applied different on each field dependent on subtype, but it looks like only those fields that are set to domains on the Unknown subtype are exposed on the reader. Subtypes that have domain fields applied to other fields, have these attributes resolved but they remain unexposed.

 

Is this a known issue?

Best answer by jamatsafe

Hi ​@ebygomm ,

Thanks for catching this and submitting a ticket as well. We’ve taken a look and were able to reproduce the same behavior on our end. Resolved attributes are only exposed when either a base field level domain exists or a domain exists on the unknown subtype. It’s now logged internally (FMEFORM-35808) for review.

For now, it seems the only way to expose the resolved attributes is to use something like an AttributeExposer. We’ll share any updates here as they come. If anyone else runs into this, feel free to add your findings or workarounds!

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

ebygomm
Influencer
Forum|alt.badge.img+46
  • Author
  • Influencer
  • December 1, 2025

If reading the schema, this also exhibits the same behaviour. Domains that are set on certain subtypes but not the unknown subtype are not returned as a resolved attribute in the schema. This is the case even if the query is restricted to a single subtype


jamatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • Best Answer
  • December 4, 2025

Hi ​@ebygomm ,

Thanks for catching this and submitting a ticket as well. We’ve taken a look and were able to reproduce the same behavior on our end. Resolved attributes are only exposed when either a base field level domain exists or a domain exists on the unknown subtype. It’s now logged internally (FMEFORM-35808) for review.

For now, it seems the only way to expose the resolved attributes is to use something like an AttributeExposer. We’ll share any updates here as they come. If anyone else runs into this, feel free to add your findings or workarounds!


ebygomm
Influencer
Forum|alt.badge.img+46
  • Author
  • Influencer
  • December 5, 2025

In this particular use case, the attribute exposer wasn’t a solution as the workspace was writing dynamically so the lack of the resolved attributes in the schema was the problem. The workaround was to use a portal connection to get the schema.