Hello, I have a few surveys set up that are meant to be submitted to by the public. We are essentially crowd sourcing information so that when someone finds that the information is no longer correct or relevant, they can request to change it. However, that means that if one person submits a change and provides details about it, a second person may want to submit a change and I would not want the first person's notes to appear where a blank question should appear. I have this set up to update the feature service directly, with a review process where the data is added or changed only after it is reviewed.
In my xls form calculation I have something like: if(${Notes}, '', ${Notes}, '') meaning to set it to empty. I can't calculate it to null by doing '' as it also throws an error. I am not sure if either are good ways to do this. The error I am getting is the XPath dependency cycle (thread here) in which Esri staff mentioned: "fields cannot refer to themselves in a calculation, as that might cause an endless loop."
Is there another way to achieve what I am looking to do? I know it's possible to collect that info in another feature layer but right now the review process is set up pretty well with my current structure. I don't believe there is a workaround (for example, having multiple fields for different notes purposes) as there is always the chance someone will request a change to the same listing.