Hey!
We are having issues with a work flow we are pursuing. The workflow being:
- Have a pre created file geodatabase, with field names and domains.
- Take data in another schema and field map it to the file gdb with the append Geoprocessing tool.
We are running into a pretty large issue where the append tool doesn't error or warn of domains being violated.
This doesn't allow us to hand this task off the people that may not have a great grasp of the underlying data / process. They end up running append, getting a success message, and saying it's all good, which isn't useful for our next steps.
Questions:
- Is the append tool not supposed to respect domains?
- If not, what are domains then? They aren't database level constraints?
- Is best practice not to use domains in this way? If so, what are our alternatives for strictly defining file geodatabase fields so no one can mess up (like an in list constraint in an sql db)?
Thanks for reading!
