Latest Contributions by Mondi_GIS

@ChristopherMask, if you set the appearance on the number you are capturing to numbers mode, for example, it makes it harder to skip to the next question without pressing enter/committing the result before continuing to the next repeat.    ... View more

I found this happens, but if you change the appearance of the field, it "forces" the user to press enter to get to the add repeat button. ... View more

Any further insights from anyone? @ZacharySutherby?    ... View more

I have managed to strip out the bulk of our form and the lookups and just have the calculation that is not behaving correctly. So far the feedback from ESRI is that it is an "expected behaviour" which I do not agree with.  On further investigation, the calculation mode behaves as "expected" when there is no appearance applied to the numeric field. When I apply the numbers or calculator appearance the calculation mode behaves as though it is set to Always instead of Auto. Because of our locale settings, we have to have the numbers appearance in use for anything with decimals.    The field of concern that is recalculating erroneously is the "lost"field.  ... View more

Hi Zach,  The whenEmpty mode doesn't work for our tool because it needs to recalculate when I change the method of defining loss (Hectares/percent/trees). I would need to strip down the xlsform significantly before I could share it because of a lot of validation and pull data functions on private data. Can I perhaps email it? ... View more

This would be a really useful function for our work teams as well. They complain often about forgetting to submit their forms when they are back online. Survey123 warns about running in background mode so I'm sure this can't be too difficult to implement. ... View more

Having the same problem after the upgrade - I have hoped an obvious bug like this would have been fixed in the new patch.. but nope! A nasty surprise for me post-upgrade!  ... View more

@IsmaelChivite please can you assist here - this app has stopped working and is causing havoc for us! ... View more

Hi Glen,    Thanks for the questions. As it stands currently: - We run script 1 which does an ETL from our editing GDB to a publishing SDE GDB and processes a view which appends attributes. This truncates and appends the table in the publishing SDE but maintains the globalIDs. THis is published to our on Prem enterprise. - A second script (which was developed by ESRI SA) checks for geometry changes between our Feature service on Prem and the Feature Service on AGOL. It then makes the Geometry changes and then updates the attributes.  Previously our script to AGOL would truncate and append but it triggered this bug (BUG-000135310 ). We have never managed to get the distributed collaboration to work on this layer either, and we couldn't tell if it was because the portal is not public facing or the size of the layer caused issues - the errors tended towards size restrictions. I have just tested again in a new map since we republished this "problem layer" with the new script. It is definitely that layer causing grief.  By troubleshooting logs - do you mean switching on developer mode and extracting logs, or just the sync error message. I haven't tried extracting the logs but could do this.  This issue has been going on for months and months now, and yes, ESRI support in SA has been assisting - we had hoped that by stopping the trunc and append approach to AGOL, it would solve this problem. ... View more

Hi Glen,  I have been struggling for months now to get our sync working. It works on a small area, but fails to sync when I try to have larger areas. The error seems to relate to our most important dataset, the register of all our forestry compartments and their attributes. This layer is not editable to the viewers, and is just there for reference purposes. I get the error:  Sync Failed Unable to synchronize replica.  Details: Sync replica internal error - (and then a number of different IDs).  This layer gets synchronised from our Portal to AGOL overnight, and we have spent a lot of time optimising the script, as it used to truncate and append everytime but we found this was causing massive replica log on AGOL and causing the file to grow to beyond 30GB. We now only edit the geometry were there were changes and then update the attributes (Age, species etc). It worked fore two weeks and I was rejoicing, and now it is broken again and I am beyond desperate at this point in time. I have all our senior management breathing down my neck, asking when we will sort out this bug and go live or should we throw ESRI out completely if their apps aren't reliable?  ... View more

@IanGallo, the problem at the time when I posted it was resolved with an update to survey123 3.12**, however, I have recently had users complaining about the same behaviour happening again. I haven't been able to replicate the error on my side, but of our users are definitely having a problem, as shown below (the red line is where the polygon should have been).     ... View more

We do run a truncate and append on our data but the problems with this are: - there is aome funny issue where the indexes keep getting bigger and bigger with every rewrite until a 200mb file is suddenly 25gb. ESRI can't seem to replicate this error so I think it is something to do with the older version of our sde perhaps? - if your network isn't super stable, it sometimes bombs out mid-delete or rewrite and not all your records get added or deleted. Sometimes our script runs 5 or 6 times before we get matching number of records You can't disable sync without breaking all the offline replicas for your maps. ... View more

We need this functionality too. We often have fire incidents that are made up of multiple polygons. ... View more