My org is switching everything to Enterprise Portal from Online, and I am working on republishing my Surveys in Portal. Along with this is a need to backload the existing data into the feature layer for the survey once it's in portal. After going to the feature layer for the Survey, I click "Update Data", then choose "Add Data", select the feature layer or table, and click next, then it just shows a blank window with "Update Data" at the top left, with "Back", "Cancel", and "Next" at the bottom. "Next" does nothing. I've tried clearing cache/cookies, incognito, and both Chrome and Edge browsers. I've tried with two different surveys, both with all the edit/update/add options turned on everywhere I can find. I am the owner of the survey. Any advice?
I think you will want to use Pro and Append with the setting to keep globalids (and hope it actually works) or all your repeats are broken. That is why I leave the built in globalid relates but also have my own key with a relate as well. Otherwise if you move anything your are in trouble. globlalid is a poor relate choice in my experience.
If you are stuck now. Add a new field in the original survey then calc over the globalid so at least you have a way to fix the repeats later. Add that field to the new form too of course.
Hope that helps
I'm not able to get far enough in the process to have the issue with the globalID. What I've done in the past in Online when I had to backload is do it stepwise, starting with the Parent table, and use a cross-reference to adjust the ParentGlobalID of each child record. Also, this issue is occuring with both a survey with a repeat and one with no repeat at all. I've attached an image with a few screen grabs showing the steps I run into on the simpler feature layer (no repeats).
I get what you are saying but you can just connect in Pro and then delete or append or whatever. Way easier.
Not what I was hoping to hear as I've had success with the original method, but I've put in a request with my org for ArcPro access so I can hopefully move forward.
Maybe an access rights issue?
That may have been unclear. I haven't done it via portal in that fashion, but I have had success doing it in Online. Our admin didn't seem to think it's an access thing.