Latest Contributions by TylerDunn2

‎01-31-2019

That worked great. Ended up going with the ID, but it works. Thanks a ton this.own(on(this.featureLayer, 'selection-complete', lang.hitch(this, function(){ var selectedCountSfaPop = null; if(this.featureLayer.id === "addressesWithResCOPermits_7269_2284_9950"){ selectedCountSfaPop = this.featureLayer.getSelectedFeatures().length * 3.02; this.selectedCountNodeSfaPop.innerHTML = selectedCountSfaPop.toFixed(2); } else if(this.featureLayer.id === "addressesWithResCOPermits_7269_2284_9950_1896"){ selectedCountSfaPop = this.featureLayer.getSelectedFeatures().length * 3.02; this.selectedCountNodeSfaPop.innerHTML = selectedCountSfaPop.toFixed(2); } else{ selectedCountSfaPop = this.featureLayer.getSelectedFeatures().length * 2.82; this.selectedCountNodeSfaPop.innerHTML = selectedCountSfaPop.toFixed(2); if(selectedCountSfaPop === 0) { html.addClass(this.domNode, 'no-action'); } else { html.removeClass(this.domNode, 'no-action'); } }})));

‎01-31-2019

Yeah it definitely could, all the layers pull in their unique title and the ID. My issue is where to code that into the script

‎01-31-2019

Would I attach that to this.featureLayer = layerObject at the start? Or would that get attached further down:

‎01-31-2019

this.featureLayer is referencing all 3 layers, that's what I'm trying to limit: It's really just the same feature service (AddressesWithCOs) added to the map 3 times, and a filter applied to each. So when expanding the console information, they all have different names (same as what's in the config file )and IDs. I just can't figure out where or how to specify. Would it be easier if they're all in the same feature service and query them out by URL rather then a layer property?

‎01-31-2019

They do all have different ID's, but when I try to pinpoint the layer, it seems like it return the ID number, or the layer name, not the actual layer: I also might be doing it in the wrong place. I've tried with layerObject.id, getSelectedFeatures(["1"]) and a few other spots. Where would be the best spot to call the IDs?

‎01-31-2019

Here's the long story with a few questions: I built a Survey via Survey123 Connect for our Code and Compliance group. They spent 3-4 months collecting data and entering surveys. They currently query for analysis off the CreationDate field that is auto generated and created via Survey123 (ex. How many Signs have we pulled in the last week). They asked for a few modifications to the Survey, which has required a schema change, so I built a new survey (Version 2) and appended the old surveys to the Version 2 via ArcPro. Before I did this, I created a CreateDate field and calculated it to preserve the original CreationDate information. Once it became appended to Version 2, all of the CreationDate auto generated to 1/24/2019 (the date I did the append). Luckily I maintained the original date via the CreateDate field. Moving forward I want to utilize the CreateDate field for their analysis, which means every time a survey is created, it needs to populate CreateDate with CreationDate information that is auto generated. Here's where my questions come in: 1) In my xls form, in order for me to run a calculation on the CreateDate field, the CreationDate field needs to be in the xls. Otherwise it throws an error saying there’s no CreationDate field. When I add the field (CreationDate) with the same name, alias, field type and read only, it barks when trying to publish that CreationDate isn’t editable Any suggestions on how to get around this? 2)In terms of the actual calculation, am I able to get away with a simple calculation like ${CreationDate} and it only gets applied to the survey that was just created? Or do I need to do an IF statement ensuring that any CreationDate = 1/24/2019 doesn’t have CreateDate changed. AKA when a new survey is created, does the calculation only apply to the new survey entry, or does it hit the whole database?

‎01-31-2019

So here's the background: I'm trying to use the Select widget to hit 3 layers in my map, but apply a different Census population to each layer. The layers are Single Family Attached (I want the selection count *3.02), Single Family Detached (I want the selection count * 3.02) and Multi Family (I want the selection count *2.82). This will allow our planners to estimate population in areas of the city. My issue is that I cant figure out a way to define which layer I want to be applying the multiplier to. When I write: this.own(on(this.featureLayer, 'selection-complete', lang.hitch(this, function(){ var selectedCountSfaPop = this.featureLayer.getSelectedFeatures().length * 3.02; it applies that to all three layers. When I console.log the layerObject, it returns the 3 layers, but I cannot for the life of me figure out how to separate the layers out for their individual Select and multiply. I see 2 ways about it: 1) have 1 layer and do 3 definition queries in the script to do the multiply. 2) have 3 layers and within the script specify which layer I'm hitting and do that 3 times. Anyone have any suggestions??

‎10-23-2018

Just sent over a zip file. Thanks

‎10-18-2018

Hey John What the best way to get all that info over to you?

‎10-17-2018

Hey John, thanks for the reply. I've been trying to run it in normal survey123 cause I didn't know if it had been pushed out of beta yet. I'll install the beta version and set it up. Question for you though, If i build a survey in the beta version, can the team in the field access it normally through the Survey123 app or do they need to download a different version? Thanks Tyler

‎10-05-2018

Is this still a issue that's only fixed in a Beta version? I've been trying to run the pulldata(@javascript) function but it's throwing errors still. Thanks Tyler

‎08-13-2018

Hey Robert Scheitlin, GISP Sorry if this has been covered, but I searched and didn't find an answer. I'm having issues getting a maximum of 1,000 results back from the eSearch widget. If I do a 1,500 meter buffer and do a search on the parcels, it should return in the 10,000s, but it always seems to cap it at 1,000. I've combed through the config and stuff and I can't seem to find where I can open this up to allowing more results. Any suggestions?

‎01-23-2018

Hey Charles Can you post your code for me to take a look at?

‎02-16-2017

Jackpot. You never cease to amaze Robert. Thanks a ton!

‎02-16-2017

It's accessing it and I'm getting the alerts in console: tc.watch("selectedChildWidget", lang.hitch(this, function(name, oval, nval) { switch (nval.title) { case "Ward 1": this.devProjectsLayer.visible = true; this.devProjectsLayer2.visible = false; this.devProjectsLayer3.visible = false; this.devProjectsLayer4.visible = false; console.log("ward 1"); break; case "Ward 2": this.devProjectsLayer.visible = false; this.devProjectsLayer2.visible = true; this.devProjectsLayer3.visible = false; this.devProjectsLayer4.visible = false; console.log("ward 2"); break; case "Ward 3": this.devProjectsLayer.visible = false; this.devProjectsLayer2.visible = false; this.devProjectsLayer3.visible = true; this.devProjectsLayer4.visible = false; console.log("ward 3"); break; case "Ward 4": this.devProjectsLayer.visible = false; this.devProjectsLayer2.visible = false; this.devProjectsLayer3.visible = false; this.devProjectsLayer4.visible = true; console.log("ward 4"); break; } if (nval.extent !== this.map.spatialReference) { var params = new ProjectParameters(); params.outSR = this.map.spatialReference; params.geometries = [nval.extent]; geomSvc.project(params, lang.hitch(this, function(geoms) { this.map.setExtent(geoms[0], true); })); } else { this.map.setExtent(nval.extent, true); } })); But it's still leaving the other layers on. Any other ideas? Would this actually uncheck the visible box in the layer list?

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by TylerDunn2

Re: Adding a Definition Query to Select Widget

Re: Adding a Definition Query to Select Widget

Re: Adding a Definition Query to Select Widget

Re: Adding a Definition Query to Select Widget

Re: Adding a Definition Query to Select Widget

Calculating off a reserved field

Adding a Definition Query to Select Widget

Re: Referencing a separate feature service in Survey123?

Re: Referencing a separate feature service in Survey123?

Re: Referencing a separate feature service in Survey123?

Re: Referencing a separate feature service in Survey123?

Re: Enhanced Search Widget Version 2.13 - 09/25/19

Re: Move the popup widow in WAB

Re: Definition Query on Zoom To/Tab click

Re: Definition Query on Zoom To/Tab click

Re: Referencing a separate feature service in Surv...

Creating a side panel with Launchpad Theme

Re: Move the popup widow in WAB

Re: How do I edit pop-up size and location?

Re: Move the popup widow in WAB