Solved! Go to Solution.
Hello! When a geodatabase view references a field to which a coded value domain has been applied, the code, rather than the human readable value, is exposed. Having made extensive use of coded value domains, this makes views useless for my environment. Does anyone know of a workaround?
Thank you!
ArcSDE1 10.0/SQL Server 2008 R2
Hello! When a geodatabase view references a field to which a coded value domain has been applied, the code, rather than the human readable value, is exposed. Having made extensive use of coded value domains, this makes views useless for my environment. Does anyone know of a workaround?
Thank you!
ArcSDE1 10.0/SQL Server 2008 R2
Since Esri enabled ArcGIS Desktop to create a view (as of 10.1, I believe), I would have expected that view to behave as any other geodatabase table behaves i.e. - to be geodatabase aware. But in this case, it's just a button which performs a non-geodatabase function.
I would have expected that view to behave as any other geodatabase table behaves
i.e. - to be geodatabase aware.
Since ArcGIS Enterprise / ArcMap 10.6 and ArcGIS Pro 2.7 (please correct my version numbers if I'm incorrect), the user has had the ability to register database views with the geodatabase. Once I register a database view with the geodatabase, I would expect that it has full geodatabase functionality, including displaying domain descriptions instead of values.
Esri Canada technical support pointed us to this example, which we've tried and it works as expected. However, I would expect that this would be implemented by Esri out-of-the-box.