Survey123 Connect Form in Edit Mode - Calculated field automatically getting updated even though trigger field is not updated

[LJackson29]

Hello - 

I have a survey123 form (Request Form) in AGO created in Survey123 Connect for users to make a request (Step 1).

(Step 2) Once a request is made, a second user then needs to go in and approve the request using a second form (Edit Form) which uses the hosted feature layer created by the Request Form - this is done in an Experience Builder app using the survey widget in Edit mode. Using a calculate function in the Status field, if the request is approved in the Approved field (=Yes), the Status field is updated to 'Model_Requested', if the Approval is set to "No", then Status field is updated to 'Request_Cancelled', otherwise the Status remains null. The bind::esri:parameters is set to "calculationMode=always" as I don't want User 2 to have to update the Status field using the calculate button.

if(${Approved} = 'Yes', 'Model_Requested', if(${Approved} = 'No', 'Request_Cancelled', ''))

(Step 3) For approved requests, a third user tracks the progress of the request using the Edit Form from Step 2 using the same EB app. The issue that I am having, is the 3rd user may update the Status to Active and submit the changes, but the next time they go in to edit the form the Status field is automatically reset to "Model Requested" (because Approved = Yes) before any changes are made to the form. Is there a way, I can prevent the Status field from automatically updating for user 3?

Sorry for the complicated scenario. I welcome any suggestions. 

[Neal_t_k]

Have you tried "calculationMode=auto"?

Survey123 Tricks of the Trade: Calculation modes - Esri Community

[LJackson29]

@Neal_t_k Yes, that resulted in needing to click the calculate button. The status question is in a different section of the form than the Approval section, so it would be easy for the the user to forget to update the Status field and/or awkward. The approval process is a recent addition to the workflow, so trying to make it as easy as possible for user 2 who has not been using the form for the past 5 years, while trying to maintain the same work flow for user 3. One option may be to just create a 3rd form specifically for User 2 but I was trying to avoid that as it just makes maintaining the overall workflow, and apps that much more complicated.

[Neal_t_k]

That's weird, I would try it again, it should only be manual calculation after a manual entry into status.  A quick test shows it does work that way at least in Connect.  Some other thoughts:

You could make a separate form for status tracking

You could consider adding a tracking status field to be used by users in step 3

You could consider doing a Dashboard for step 3. You can configure editable Dashboards, and step 3 users could then see an overview of all projects and statuses. 

[LJackson29 · Accepted solution]

@Neal_t_k I know, based upon everything I have read it should work (I am using connect), but it's not - I tried a few different times. Not sure if it is user error or a bug. I ended up just creating a 3rd form - its cleaner and easier for the user, just more for us to maintain on the backend.