I'm trying to import feature layers from a Geodatabase that contains subtypes and domains into a third party application. However, the third party application does not recognize subtypes. This results in any field that has the domain designated via the subtype properties and not the field properties results in just the coded value of the domain and not the description in that field.
At this point after much playing the only way I have figured out on how to get this to import correctly is to run the below workflow on each individual subtype:
As you could imagine this is going to be quite the process to get this all accomplished and before I go through the process and try to set up some automation with python as I will need to repeat this task periodically to push updates; I was wondering if anyone knew of any additional tools or setting that I'm missing that could combine a few of these steps or automate this better?
For the Environment Setting, Transfer field domain descriptions (Environment settting), this only works if you're output is a shapefile or a dBASE output. What is your output format?
I was using the Export Features tool which only allows to export from feature class to feature class. What I found as I have been playing with it the last few days that I have been having some extreme inconsistency when running this tool. (Pro 3.2.0). One day when running it and exporting it to a new blank file geodatabase the subtypes and domains transfer over, yesterday I tried it again, the subtypes were transferring but not the domains within the subtypes and only the domains that was listed in the field properties transferred. Now today when I try it no matter the settings all subtypes and all domains are transferring.
I will look into to see the 3rd party software can take shapefiles as I see now when I run the Feature Class To Shapefile tool it does add those additional fields with the domain descriptions when that field is checked.
Thank you for the feedback/response. That is rather odd with the inconsistent output results. Whenever I see strangeness afoot like this, I do a soft reset of ArcGIS Pro. You can learn more about that here.