In a geodatabase with tables configured using classic 1-M relationships, it would be convenient to have data entry in a "child" table use a drop-down list of values from its "parent" table. For example, when creating an Invoice, have the Customer drop-down list populated from the latest values of the Customer table. This is such a common pattern in relational database systems, that I was surprised to find Esri cannot populate coded-value domains using a regular geodatabase table. I've searched high and low and opened a support incident to find a workaround, but none appears to exist (I'd be happy to learn otherwise). To be manageable, this needs to take effect at the database level so that the latest values are available whether the parent table (Customers in the example above) is edited in Pro, in Map Viewer, via a GP tool, etc. And the logical construct seems to be a coded-value domain where the values are not hard-coded, but come from a geodatabase table or feature class attribute table. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.