Latest Contributions by NatalieScott1

So this is following on a little from this question: Edit Widget maybe broken in new Web Apps? Which I thought I had solved, but am now having more issues with. I have a web app that has a single editable layer in it. 1. I open the app, open the editing widget, click on a point - the point is editable 2. If I search for an address, the map will zoom to it but then I can't click on any points to access the Edit window - even after clearing the geocoder search bar. All points come up with the result from the geocode: I searched for 50 Kilmore and then cleared the Search Bar. All points now return this popup. 3, The workaround I've found is to exit and re-enter the edit widget, at which point the points become editable again. Does anyone else have this problem or, better yet, a solution? Jianxia Song​, this might be one for you... Thanks! ... View more

I've noticed in the update to the Web App builder last Friday, the Geocoder has a slightly odd behaviour. I have it rigged up to a custom address locator. When I put in part of an address and search, it returns the full address - so far so good. But in order to zoom to that address, I am required to click on the part of the address that is not in bold, as follows: Here I have to click 'Rolleston' Here I can click 'Crescent, or Spreydon', but not '12 Evesham' Has anyone else noticed this behaviour and, if it's a bug, can it please be fixed in some future release (Esri..?) Thanks! ... View more

Hi, I'm curious if anyone else has experienced this issue. I have a web app (created in Web App Builder) that has a number of layers, of which some are editable. The workflow is that the user turns on the editable layer(s), opens the edit widget, and can edit (create/delete/update attributes) the lines in the map. This workflow broke last Friday and I'm at a loss to work out why. What happens now is that it seems that if I make any changes to the TOC and adjust the map zoom, the edit widget and the popups don't work anymore. If I turn on an editable layer and go into the edit widget,  I simply see 'Feature creation disabled for all layers'. When I click on a line, there is no response (there should be popups on all layers). In the webmap the popups and edit work as normal. Additionally, in the Web App it will usually work well until I adjust the zoom scale. These Web Maps and Apps were published in the prior version of ArcGIS WebApp Builder (ie before Friday's update) but have been edited in Web App Builder since Friday's update, which is what makes me suspect the update might have made some changes. Has anyone else experienced anything like this? Any ideas? Thanks for your help! ... View more

I have a GP task that is called within a JS webpage. When I click the button to run the task, it frequently starts up multiple version of the task as shown in the following console logs:   (for context, FP13 is the js page; line 927 is "console.log(jobInfo.jobStatus);" and the '2' or other number that sometimes occurs in front of the output indicates that that statement has been console.logged that many times in succession)   2FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting 2FP13.js:927 esriJobSubmitted 2FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting 2FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted 2FP13.js:927 esriJobExecuting 2FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted 2FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting 2FP13.js:927 esriJobSubmitted 2FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted FP13.js:927 esriJobExecuting FP13.js:927 esriJobSubmitted 31FP13.js:927 esriJobExecuting FP13.js:927 esriJobFailed FP13.js:932 esriJobFailed 19FP13.js:927 esriJobExecuting FP13.js:927 esriJobSucceeded FP13.js:932 esriJobSucceeded (etc etc)   So you can see that the task was sumbitted multiple times and is running many of these concurrently. Some of them succeed, some of them fail. There is no consistency to the number of times a job is sumbitted - it might be once, twice, or any number.   The GP task is called with: gpEvent.submitJob(paramsEvent, eventCompleteCallback, eventStatusCallback); The parameters are unlikely to be the problem because doesn't behave consistently even when the parameters are identical.   Has anyone come across this behaviour before? And how do I fix it?   I am running the GP service from a 10.2.1 server and testing primarily in Chrome using the 3.11 API build.   Many thanks! Natalie     ... View more

I have a web page with a map where I want to be able to click on the map and get certain attribute values of the feature that I clicked on. EG I click on a property and can access the property name, zone, owner etc. These are all attributes in the data. The purpose for this is to pass the attribute values to another part of the web page. So far I have tried a lot of variations on query/infotemplate/attributeinspector tasks. It is easy enough to get the values in a popup but I am having trouble accessing the values themselves in a way that I can use them elsewhere.           var buttonCreateReport = doc.getElementById('btnCreateReport');           buttonCreateReport.addEventListener('click', function createReport(){             reportToolbar = new Draw(map);             var reportQuery = new Query();             reportToolbar.activate(Draw.POINT);             on(reportToolbar, "DrawEnd", function (geometry) {               reportToolbar.deactivate();               reportQuery.geometry = geometry;               var reportTemplate = new InfoTemplate();               reportTemplate.setTitle('Report');               reportTemplate.setContent("${Property_Name}");               myGraphic = new Graphic();               myGraphic.geometry = geometry;               myGraphic.infoTemplate = reportTemplate;               myGraphic.attributes = '["Name": {Property_Name}]';             });           }); Can anyone give me any help? I am happy to scrap this code and start again if I'm completely on the wrong track... but I have a distinct feeling that I'm just missing a small piece of the puzzle somewhere. Thanks! ... View more