Pretty simple data export, I have a reader referencing some SDE data and then a writer to a file geodatabase. But reviewing the attributes in the file geodatabase I see that the domain attributes are the codes (1,2.3, etc) not the descriptions (copper, steel, PVC, etc).
Is there a way to write the domain descriptions and not codes?
The same is true for the subtypes, it is writing the code (1,2,3) and not the description (tap, bend, saddle, etc).
Best answer by sammy
In the Reader > Properties > Constraints > Resolve Domains.
Looks like this preserves the domain descriptions but unfortunately does it by creating duplicate fields with appended names, which in our case is a show stopper.
Also noticed that for some reason it was not applied to all fields with domains.
Also noticed that 'Resolve Subtype' dosn't appear to work.
Just some notes in case anyone else comes across this. If you aren't restricted by strict naming conventions you can get the data out with domain descriptions.
@000craig I am dealing with the duplicate fields you mentioned in 2 steps:
There may be a more efficient way to do that but this works for what I need.
In the Reader > Properties > Constraints > Resolve Domains.
Looks like this preserves the domain descriptions but unfortunately does it by creating duplicate fields with appended names, which in our case is a show stopper.
Also noticed that for some reason it was not applied to all fields with domains.
Also noticed that 'Resolve Subtype' dosn't appear to work.
Just some notes in case anyone else comes across this. If you aren't restricted by strict naming conventions you can get the data out with domain descriptions.
+16In the Reader > Properties > Constraints > Resolve Domains.
Looks like this preserves the domain descriptions but unfortunately does it by creating duplicate fields with appended names, which in our case is a show stopper.
Also noticed that for some reason it was not applied to all fields with domains.
Also noticed that 'Resolve Subtype' dosn't appear to work.
Just some notes in case anyone else comes across this. If you aren't restricted by strict naming conventions you can get the data out with domain descriptions.
Can I ask what specific reader you are using and what version of FME you are using?
I am also having an issue where some of my fields are not being resolved.
I am using FME Workbench 2023.1 and using an ESRI ArcGIS Portal Feature Service Reader to read in Utility Network Data.
I have 3 attributes that are not successfully resolving:
So I am curious about the details of your resolving domain issues as I am trying to troubleshoot my issues.
+16Can I ask what specific reader you are using and what version of FME you are using?
I am also having an issue where some of my fields are not being resolved.
I am using FME Workbench 2023.1 and using an ESRI ArcGIS Portal Feature Service Reader to read in Utility Network Data.
I have 3 attributes that are not successfully resolving:
So I am curious about the details of your resolving domain issues as I am trying to troubleshoot my issues.
Oh, actually, I just saw the comment on that thread I mentioned above that said to expose the format attribute "arcgisonline_subtype_name" in the reader if you want the Asset Group subtype description to be added as a field. I did that and it worked for me.
Now I just need to figure out how to get the other two fields working.
+16Can I ask what specific reader you are using and what version of FME you are using?
I am also having an issue where some of my fields are not being resolved.
I am using FME Workbench 2023.1 and using an ESRI ArcGIS Portal Feature Service Reader to read in Utility Network Data.
I have 3 attributes that are not successfully resolving:
So I am curious about the details of your resolving domain issues as I am trying to troubleshoot my issues.
Following up about my issue with the text, coded domain that was not showing any description values in fme (issue #2 on my list above). The problem is actually with the domain definition in the feature service not with the fme reader. So I have to fix my feature service to resolve this issue.
Also, for the range domain field (issue #3 on my list above), I think that it is correct that there won’t be any values for fme to resolve as there aren’t any code-description definitions for this type of domain. So this is also not an issue with the fme reader not working correctly.
+16In the Reader > Properties > Constraints > Resolve Domains.
Looks like this preserves the domain descriptions but unfortunately does it by creating duplicate fields with appended names, which in our case is a show stopper.
Also noticed that for some reason it was not applied to all fields with domains.
Also noticed that 'Resolve Subtype' dosn't appear to work.
Just some notes in case anyone else comes across this. If you aren't restricted by strict naming conventions you can get the data out with domain descriptions.
@000craig I am dealing with the duplicate fields you mentioned in 2 steps:
There may be a more efficient way to do that but this works for what I need.
@000craig I am dealing with the duplicate fields you mentioned in 2 steps:
There may be a more efficient way to do that but this works for what I need.
Hi, thank you for providing more information on this process. Sorry I wasn't able to provide any help, FME is new into our operations so were still in a learning phase. I will definitely review our process and see if we can revive with your input, thanks!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
