Latest Contributions by WengNg1

Just bumping this up to see if anyone else is having the same problem? When you tap on a feature in Collector, the label underneath the popup-title is set to weird fields (lat/longs for points) and area value for polygons. Previously on Collector (Classic) , I can change this field by modifying the display field before publishing the feature service. The new Collector doesn't seem to be honouring this field. ... View more

Hi , With the upgrade to TLS 1.2, will ArcGIS Online then be unable to communicate with any published services in ArcGIS Server running the old 1.1/1.0 protocol (e.g. 10.3 and below?) Thanks, Weng ... View more

I had this issue as well and my maps and feature services are on AGOL. A good way to tell which layer is causing issues is in the error code. In the case above, layer 0 points to the first layer on the map. In my case, it wasn't a geometry issue but a field name in a hosted feature service that was converted from an Excel spreadsheet that caused it to fail when creating a replica. ... View more

For those who are still looking for a solution and are on AGOl , here is what I found worked : 1. Logging out and then logging back in fixes the issues most of the time. It has something to do with an expired token potentially. 2. Resetting the password of the named user if step 1 didn't work.  ... View more

We're having the same problem as well and I'm still scratching my head over this as this updates are not registered back into the feature service plus the offline map reverts back to an older version of the database (minus all new data). This has happened randomly and I haven't been able to replicate this yet.As our feature services are hosted on AGOL, it would be great to get into the logs to check what exactly happened and if there is a way we can recover the files. ... View more

Hi, I'm attempting to do the same thing through ArcGIS Python API. I succeeded in changing the 'Keep track of who created and last updated features' through an update definition call using the API.  However, I was unable to locate the property that defines Keep track of created and updated features .  What should I do to enable that property? ... View more

I have a field worker having the same issue . The issue just appeared as of yesterday when he has been out in the field for 1.5 weeks collecting and syncing data. Tried using a better wifi , turning it back off and on again and still doesn't work. Is the issue potentially a token thing that has expired in Collector? ... View more

Hi Kylie, Please find clarification below :  Could you clarify for me what you mean by:    > This was somewhat cumbersome as I have multiple copies of the dataset that I wanted to add to my offline map. Using a hosted feature layer view doesn't create a new copy of the dataset, but allows different uses of the same data. What I meant was everytime I want to copy a layer and add additional filters, I have to create a hosted view in order for Offline mode to work as intended on Collector. For example, if I want to copy a layer twice and filter and differently, I have to(as an owner) of the layer create 2 views and add them into the map. > the views that I create in Offline mode also does not update the parent feature layer after editing although it is coming from the same dataset. It doesn't seem to recognise any parent/child relationship   Could you explain a bit here? What are you doing to create views in offline mode, or do you mean when you create features while offline? Could you explain the data you are using, and the parent/child relationship and which features you are making offline? Following the example previously, say if I want 3 copies of the same layers, I will need to create 3 views and add them into my map.  As I update layer 1, layer 2 and 3 does not update accordingly as it doesn't recognise that all 3 layers are from the same layer. So in offline mode, the relationships are not really recognised . However , if I ignore the fact that filters are not supported and went ahead and just made a copy of the layer and bring it offline , the layers dynamically updates in offline mode as it knows it is the same layer.  Regards, Weng ... View more

Quick update : I've contacted ESRI support on this issue as well as consulted IT within my organisation. We were able to narrow it down to an issue with a new McAfee deployment from IT. This issue was successfully replicated on multiple machines within the organisation and is independent of the script's code. It will randomly corrupt the feature class if you try deleting multiple fields manually in large dataset . We suspect that it might have something to do with a memory scan of some sort but obviously that is very difficult to log. The only way that stops McAfee from blocking it was to turn off On Access Scanning and Script Scan. However, due to company policies , this cannot be the solution. We've also tried excluding all possible folders related to ESRI but still no luck. Also, this is independent of ArcMap versions as well. I've tried it on ArcGIS Pro and it was coming up with the same issue. Although not fully tested, I've encountered this issue with other tools as well when working with large datasets. So, it is not specifically a tool failure of any sort. ... View more

Hi Robert, I do have a proxy setup but I tested the widget outside of the organisation and it still doesn't work. It does however work on some map service layers. The code died at : doQuery_SupportOrderByAndPagination: function(a, b) { var e = new f , c = n.hitch(this, function(a) { console.error(a); --------------------> CODE DIED HERE e.reject(a) }) , d = this.currentAttrs.query.relationship; this._queryCount(a, b, d).then(n.hitch(this, function(k) { this.currentAttrs.query.allCount = k; 0 === k ? e.resolve([]) : (this.currentAttrs.query.nextIndex = 0, this._queryWithPaginationAndOrder(a, b, 0, this.currentAttrs.query.maxRecordCount, d).then(n.hitch(this, function(a) { a = a.features; this.currentAttrs.query.nextIndex += a.length; e.resolve(a) }), c)) }), c); return e }, Through Fiddler, I notice that it failed at the query request on the Feature Layer and not the Map Service layer with a code":400,message -Unable to perform query. Please check your parameters. Not sure what is causing the issue, perhaps a dodgy syntax? I was able replicate the exact same error by doing a Select By Location on ArcGIS Pro using those two layers. Just to clarify, the feature layer sits within AGOL whilst the map service sits in an external organisation. I've built the the query using the standard Query widget with date inputs by users and a spatial relationship intersect with a map service hosted externally.The feature layer is quite large with about 1 million polygons. ****************UPDATE : Potentially Size Related ************* I adjusted the date queried so that it returns a smaller result and I was able to obtain a result from that. So, it seems to me that something is falling over due to the large feature layer queried. ****************UPDATE: Temporary Workaround****************** I did manage to find a workaround and it involves creating two Query widgets , the first one would create a query of the first feature layer and then the second one would intersect the results of the first layer to return the results required.  That worked fine but it's not something I was hoping I would resort to.  Thanks, Weng ... View more