I have an advanced license so I don't think it comes down to licensing.
I have not been able to resolve this issue. I gave up and started waiting for Pro 2.4. Maybe it will be fixed...
Plus through my field applications it became apparent that there is still a lot of troubleshooting to be done with subtypes and domains. For myself, I think that using contingent values when they're still so new in the program will only lead to data extraction problems down the line.
Since using the Collector app, I have realized that my domain descriptions are lost when I revert my data back into Desktop or Pro unless the same domain is applied across all fields. The program allows you to selectively apply domains to specific fields based on what subtype was selected in the subtypes view. This function made my data collection templates in Collector super precise and extremely user friendly. Applying domains in this fashion worked great for the data collection part.
However, when it came time to revert data back into a FGDB I could not get domain descriptions out for any domain that wasn't applied across an entire field. From both a data management, and field collection perspective, it was a huge bummer.
I had to rework my data collection template so that every domain had its own field. And for my data, each subtype has its own set of location domains, among other things. So you can imagine the number of unused fields I have for each collection point. My template is long and clunky and requires a lot of back end clean up after it's exported into Excel.
But hey, at least my domain descriptions are there!
So given this experience, I am going to hold off on implementing contingent values into any of my data collection templates until I know it's a functioning feature (from a data management perspective).
Good luck!
