My output feature service has a field ADDRESS_ID which is unique. Yet the data pipeline is refusing to accept it as unique. So it Errors.
Why won't it accept the unique ID for add?? GAHHHHH
This pipeline was working just dandy, but I had to modify a relationship class in the service so I created a copy since it's a live workflow, published the new one to arcgis online and was just swapping to the new service when this issue started happening. Nothing significant changed between these too and I've made sure that unique required setting is on. Am I missing something super obvious?? This is such a basic flow.
Like I mentioned, I simply swapped the output source to my new feature service when the issue started happening. The pipeline works just fine connected to the original output source which has identical settings 😭
I did add a relationship class that uses ADDRESS_ID as a key to my new service. So that like what... makes it unable to run datapipelines or something??