-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Domain Mapping rework Testing #249
Comments
Every time I click the Load Domains button it adds the layers for the source and target to the map. I understand this is because of a limitation we encountered with get the domain from the feature class in the Pro .NET api. However, it seems necessary to have to add the layer (resulting in duplicate copies of the layer) every time to button is clicked. It might not make sense to click the button multiple times for the same field, but perfectly reasonable workflow if you have multiple fields with domains. |
More of a question because I expected different results, but if a value doesn't have a corresponding value in the domain target and you leave it set to (None) should the value still be copied? See the example below where in the source the Domain has a code of 1, description Monday. If I leave the target set to None, I would expect any values of 1 to be set to null when appended to the target source. However, what I am seeing is the value of 1 is written to the target even though that value doesn't exist in the target Domain. It behaves more like Copy in this sense. |
I think it does act as a copy, so a code unmapped copies as is. |
Related to my first comment above, once I have loaded the domains and set the mapping if above I select another field from the table above and then re-select the field with the domain mapping I triggers both layers to be loaded into the map again. It seems like we could read these values into memory rather than having to load the layers each time. |
Other than the comments above everything functioned well and I was able to map between domains successfully. |
The text was updated successfully, but these errors were encountered: