The release of version 3.25 has brought some problems for us. To begin with, some calculated fields are malfunctioning (photo 1), in this case a date-to-text conversion.
On the other hand, and perhaps more importantly, some services with relationship classes have lost their connection, and the form no longer recognizes them. A simple test revealed that when creating a new form with all the fields (including those from related classes), the relationship schema used for submission works without issue (image 2). However, if you remove those fields from the relationship class in the form, the service is submitted without the connection (image 3).
Hello @IDEMuniMendoza,
Can you please verify when you are submitting surveys are you using the Survey123 web app or the field app?
On the second issue noted regarding the submission of related records is your survey configured with a submission_url?
Hey @IDEMuniMendoza,
Thank you for verifying you're seeing the issue in the web app! For the first issue where you're not seeing the calculations run I see you commented on https://community.esri.com/t5/arcgis-survey123-questions/webforms-not-running-calculations/m-p/16929... I think this is the same issue. If you try setting calculationMode=always under the bind::esri:parameters column for your "f_sin" and "f_act" questions does that work around the issue?
On the second issue of data not submitting to the related table I don't believe I'm reproducing what I interpret as the scenario. I have a hosted feature layer with a parent layer and 3 related tables and when I create my survey based on that hosted feature layer the schema I see in Connect is:
Which I believe is equivalent to your image 2. I removed table1 and table3 from my form design only leaving table2 and published the survey:
When I submit a record in the Survey123 web app I do see the related records come through in table2
A couple of things to cross reference:
Hi @ZacharySutherby,
I'll explain in a little more detail... This is an unhosted service that has an ObjectID to GUID relationship...
What you replicated is correct, and it's the same thing that's happening to me, but perhaps I didn't explain the problem well at the time.
This service populates two Survey123 forms. The first is for registering traffic accidents, and the second is for validating and correcting any errors that may have arisen (this form is edited).
When we created both forms, in the case of the validation form, even though I didn't include the fields with repeat values, I still saw them published in the schema and in the data query.
Now it doesn't recognize their existence.