Duplicate feature layer after re-publishing form

[Daniel_Perkins]

Hi all, any help appreciated. 

I have an existing Survey123 form published with Survey123 connect (using AGOL). When I make changes to the XLSform which change the data schema, I get the normal warning dialogue box which says "The existing feature service is not compatible with the survey." When I check the slider saying "I understand the existing feature service will be deleted" and Publish, all seems to work. 

However I now have two matching feature services in AGOL with the same name. One has the old data (collected prior to the re-publish) and it stays static. The other one has all data going forward. The only difference I can see is the data itself and the modified date. I have scoured the help documents and I don't think this is by design, but perhaps it's a new release feature? I can see why it would be good in concept, but it's causing issues for me, which makes me think it's a bug. 

This has happened to me twice now. Any thoughts welcome, thank you.

[DavidPike]

I think it should be deleted but it's been a while.  It may be due to delete protection being on the Hosted Feature Layer.

it shouldn't be a weird duplicate in any case, rather just another hosted feature layer with the same name.  The XLS should point to the new service.  You'll see different endpoints in the REST interface e.g. service_784373byg478erjgjrg439

You should see the new endpoint referenced in the .iteminfo and debug\createService.json files in MySurveyDesigns folder for your Survey.

[Neal-Kittelson]

I have noticed this too.  I just checked and there are no delete protections on mine.  I assumed it was an archiving feature that was new cause it hadn't happened in the past.  If it is a feature, it would be nice to have the file renamed to something else because it is confusing have multiple with the same name.