Latest Contributions by HamishMills

Hi again PWong-esristaff‌, I have done everything I can to make sure that my locale is set correctly, however the incorrect date format (MM/DD/YYYY) is still the only option allowed by the field input. Are you certain that the Batch Attribute Editor widget is affected by this update? I've noted that the date picker is now fixed and works correctly however the date format still doesn't reflect my 'locale' correctly and I am unable to override this. Cheers Hamish ... View more

Hi Previn,  I have recently downloaded the latest WebApp Builder Dev version 2.2. However on initial testing I have found that the date format has not been updated. I still find that once I have selected a date from the date picker it shows in the incorrect format (MM/DD/YYYY).  Unless I am incorrect, is the date field now something that should reflect my local date format? Cheers Hamish ... View more

Thanks Previn,   This code works partially but all I really need is the section of code that will stop the field from locking the save button when users enter dates in the DD/MM/YYYY format. The date picker doesn't actually function so using the date picker is not an option at this point. Users will be typing the date in manually until the new release comes out.    In any case, I understand I've taken a lot of your time on this issue so I'm happy to wait for the new release, as long as its coming out in the first 2 weeks of October.    Thanks again Hamish ... View more

Hi Previn, Our users do not use ArcGIS Online at all. We only use apps deployed on our own Portal 10.3.1 installation. The reason I need to use WAB Dev is because the 'Batch Attribute Editor' widget is not available in the built in WAB on our Portal. Therefore I need some other way to change the widget so it functions correctly for my users.  If you read further back up the thread you will see that my issue is not just related to what's in that code block, i.e. the date hint text. My main issue is that users are unable to input the date at all in a format they are familiar with. Currently if you input a date in the 'DD/MM/YYYY' format the widget does not allow you to save these values because the field is flagged as incorrect and the save button is then locked/greyed out. See the image below:  I need some way to stop the field turning red and locking the save button when I enter dates in the 'DD/MM/YYYY' format.  Thanks  Hamish ... View more

Thanks Lemao.  Hopefully Xiaodong_Wang-esristaff or PWong-esristaff‌ will be able to assist. I have a large user base waiting on this fix so the sooner you guys can help me out the better!   ... View more

Hey Robert, Thanks so much for your quick response. While this info has allowed me to update the suggested date text, meaning it shows the user what should be input. It still does not allow the user to input dates in the DD/MM/YYYY format. I need to find where or why this restriction is being placed on the field. See the image below. If the user enters the date in the required format the field entry box turns red and does not allow it to be saved.  If you could point me in the right direction I would be so appreciative. (I should probably mention at this point that the date picker does not actually work with any date format, this is possibly because of an active bug? I am planning on having my users just type the dates in manually because of this. See: Batch Attribute Editing Dates in WAB 2.1 and BUG-000097696: The Batch Attribute Editor widget in ArcGIS Web App..) Thanks again Hamish Mills ... View more

Thanks for your suggestion Blake. I was pretty sure this was not the case but have double checked just to be sure. So just to confirm, no this is not affecting the address format of the widget.  ... View more

BUMP! ... View more

Hey Everyone, Bit late to this thread but there's not much else I could find relevant to this issue, so thought it worth a post. ------------------------------------------------------------------------------------------------- We have a script that creates one map per job, on average this is 5 jobs per user at a time. Offline maps are set to create sync versions per 'user' though (i.e. multiple maps but only one sync version per user). Note: all of these maps are almost identical except for their map name, map extent and bookmarked work area. I found that out of 6 field users, only 2 users had this error appearing. Also once this error appeared for one map, it seemed that it would then appear when syncing any one of their 5 job maps. I used the suggestion Carlos Porras and Danielle Kulas had been discussing, to re-enable editing on un-editable layers. I only went into one of the 5 maps and re-enabled editing on the one reference item we have. Then to my surprise this not only allowed this map to sync but seemed to have a roll on affect and all maps were then syncable for that user. I also agree strongly with Carlos Porras's comment  "try to sync on a good wifi connection". We have seen a lot of evidence that proves that syncing on a weaker WiFi connection will have a far higher chance of causing syncing issues. TL;DR: I re-enabled editing on the only un-editable layer in the webmap, then was able to sync. Thanks! Hamish ... View more

Hi Linus, I also kept having this issue with a python script and found this thread while searching for a resolution. I eventually fixed the error by removing a ".lower()" that was connected to the version names. The ReconcileVersion_management tool is case sensitive and if you your input is changing the version name string capitalization in anyway you will get this error. Not sure if this will apply to your situation but thought I would share just in case it does Cheers Hamish ... View more

Hi Scott Prindle, After extensive investigation we believe we have tracked this issue directly to the sync process itself. So there is no issue uploading the data to the sync tools scratch folder (ArcGISServer\v10_3\directories\arcgissystem\arcgisuploads\services\{folderName}\{featureService}.FeatureServer). The error definitely occurs when the sync tools then starts to try reconcile the changes to the offline version. The errors in the sync seem to be caused by making changes to features that participate in a geometric network and were created before the map was downloaded. So generally for us this means features that were created on their desktops (in ArcMap) prior to the users going out into the field. What we believe may be happening, for example, is you may have a line feature (network cable) snapped directly on top of a point feature (power pole). These 2 items are seen seen as connected in the geometric network. The iPad user may then want to change the location of the point in the field. However when they move the point without the cable they are forcibly breaking the geometric network. Even if they attempt to snap the line back on to the point after they move it, they are unable to do so as snapping is not available in collector (unsure if this would fix the issue anyway). Let me know if you have any further ideas regarding this issue. Thank you Hamish Mills ... View more

Hello again, Just an update, after more extensive testing it does not seem to simply be the size of our syncs that is causing our errors. I have done a full debug now and attached is a detailed example of the main error we are getting. Totally unsure at this point as to what is causing this error, testing does not seem to give us a definitive answer. This error seems also intermittent but is occurring on 50% of all syncs. Note: This does not mean that if users try multiple times it will work in the end, usually once an offline map is failing its sync it will continue to fail. Still awaiting help or any suggestions anyone has. ... View more

Hi Miaogeng Zhang, We did try full debugging a few days earlier but it did not provide any more detail than the errors already showing in the logs page. I will do some more full debugging today when users are attempting to sync.  ... View more