|
POST
|
Jeff, Thanks for boiling down the issue. It is not a jsapi issue. We should add searchTemplate="${Match_addr}" to make it come up with human-friendly names for custom geocoder. This will be addressed in the next AGOL release. Jianxia
... View more
08-08-2017
04:55 PM
|
1
|
3
|
3888
|
|
POST
|
Robert, Thanks for the fixes. We will look into it. cc to YMa-esristaff Jianxia
... View more
07-31-2017
07:55 PM
|
0
|
4
|
3800
|
|
POST
|
Hillary, We are working on a blog to walk through creating a custom widget from Report dijit. Will try to publish it asap. Jianixa
... View more
04-12-2017
12:14 PM
|
3
|
6
|
3846
|
|
POST
|
This is a regression introduced in AGOL 5.1 update. We will fix it in the patch tomorrow night. Sorry for any inconvenience.
... View more
03-13-2017
06:23 PM
|
1
|
1
|
1687
|
|
POST
|
This is a regression introduced in AGOL 5.1 update last week. We will fix it in the patch tomorrow night. Sorry for any inconvenience. Jianxia
... View more
03-13-2017
06:06 PM
|
2
|
2
|
5304
|
|
POST
|
You are right. The screenshot is not right. We will update it in the coming dev edition release. Thanks!
... View more
09-20-2016
06:47 PM
|
0
|
0
|
1101
|
|
POST
|
Chad, One option is to use the Incident Analysis widget and only configure the Summary option (without Weather, Proximity or Closest Feature). This will allow the user to draw a point, line, polygon and get similar summary information. Does it work for you?
... View more
09-06-2016
03:21 PM
|
1
|
1
|
1492
|
|
POST
|
The issue has been fixed at app level and will be available in AGOL September release and Developer Editon 2.2. Thanks,
... View more
09-01-2016
05:23 PM
|
0
|
3
|
3410
|
|
POST
|
Information from JSAPI team: This is a known bug that chrome introduced at Chrome 52. Here is the active chrome 52 bug around this issue. https://bugs.chromium.org/p/chromium/issues/detail?id=633696 It references a duplicate issue that exhibits the behavior we are seeing in comment 15. A patch is under review in chromium. The workaround is to bust the cache by introducing a timestamp in the request. The bug also does not show up if you submit the second request in another context. The fix may be in a patch for chrome 52.
... View more
08-24-2016
06:22 PM
|
1
|
0
|
3410
|
|
POST
|
We will document it in the coming 2.2 release. Thanks!
... View more
08-16-2016
05:45 PM
|
1
|
0
|
2169
|
|
POST
|
Robert-- Thanks for the correction. The code update will be applied in the mid of August. Jianxia
... View more
08-02-2016
03:08 PM
|
0
|
0
|
3009
|
|
POST
|
Barnaby, I was not able to reproduce the issue with Chrome 51.0.2704.84. What's the error in the console? Thanks, Jianxia
... View more
06-10-2016
12:25 PM
|
0
|
6
|
3768
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | a week ago | |
| 1 | 2 weeks ago | |
| 2 | 2 weeks ago | |
| 6 | 07-09-2026 01:45 PM | |
| 1 | 07-07-2026 09:39 AM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|