Hi All,
I am having an issue republishing a survey the a data type change in the feature service. I sure this worked smoother in the past, but this is what I hit over the last few days...#survey123forarcgisconnect
Background:
Published Survey from Connect 3.3.51 on Win 7.
Inbox survey but collected initially as a new survey.
Shared for Viewing to another group in my organization
Change Required: Integer to Decimal
Process:
Changed an “bind::esri:fieldType” from esriFieldTypeInteger to esriFieldTypeDouble
Accepted the Warning and Published…
Publishing hung at this screen (hit red X to kill after a while):
Duplicate Feature Layer created, but not shared.
Accepted the Warning and Published again…
Publishing completed successfully.
A third duplicate Feature Layer created, but not shared.
Data collected by survey owner goes into top unshared service.
Data collected by survey user hangs on send. Have to kill Survey123 3.5.177 on IOS.
Share top Feature Layer with Group again. Send Survey from Outbox successfully.
2 surveys show in Survey123 Web Data for owner.
0 records show in Survey123 Web Data for user.
As owner unshare Viewer rights for user group.
As owner reshare Viewer rights for user group.
2 records show in Survey123 Web Data for user.
Manually Delete 2 extra Feature Layers. Error:
Some items were not deleted because they are delete protected or have dependent items.
Delete Stakeholder view.
Delete bottom Feature Service
As owner reshare Viewer rights for user group.
All seems good again…
I am sure I have republished surveys with no problems in the past...
Larry
Hi Larry,
This issue with publishing can occur when a form was initially authored in the website and then subsequently edited in Connect - you can make a copy of the survey as a workaround in this case.
During republishing, I've been stuck at the publishing screen for 30 minutes now. There are about 1,400 records in my feature layer. Is it normal to take this long deleting the service item, or should I abort and try starting over or try copying the survey?
Hi Brian,
This most likely means there was an error that was not caught by Survey123 during the deletion process. One reason is if there is a view attached to a feature layer. You can go into your item contents and manually delete the view and feature service (normally you can identify that by the last modified date).