Latest Contributions by NickDierks1

I haven't been keeping up with S123 lately, so I'm not too familiar with the new question types. You're right that the workaround shouldn't be able to apply to your situation as neatly. Is there a way to check whether or not a geoshape question has been answered? I know you can do this with non-geo questions. Basically a hidden question doing an internal check "Geoshape is null?" or something like that. Set it up so that it only checks when the data source is not a map, and constrain it so that it throws an error when the geoshape has not been answered. Those are a few big ifs (checking the status of a geoshape answer; how conditional constraints are handled), but hopefully they'll lead you toward a solution! ... View more

So, if I'm reading this right, you want any "Needs water" point to be symbolized based on year, and any "Complete" point to have a single symbol, regardless of year created? If so, that should definitely be doable. First, is the year you want to use in its own field, or part of more complete date field? If it's the latter, then be sure to use Year(datefield) to extract just the year from the rest of the date. Next, your Line 6 in your sample doesn't need to be an else if. If you change it to just else { , your code works just the same (because the else case is always going to trigger at  >14 days). Whether or not you change Line 6, the solution lies in changing Line 7: result = "Needs Water " + [year] (with [year] being your year field, or Year() function mentioned above) This will give you the following results: Complete Needs Water 2017 Needs Water 2018 Needs Water 2019 Go ahead and assign colours in your map as you wish. Let me know if this helps, or if you're looking for something a little different. ... View more

There's this blog post, that shows how to put a simple bounding box around a specific area: https://community.esri.com/groups/survey123/blog/2017/10/26/limiting-extent-in-which-input-point-can-exist  If you want a more specific border, and are willing to use a geocoding service (uses credits for ESRI's World Geocoder), you could use the pulldata() function to grab location information from the geopoint and then utilize a constraint to make sure it's within the state you want. https://community.esri.com/groups/survey123/blog/2018/07/06/understanding-reverse-geocoding-in-survey123-30  ... View more

For the line existing_prog_a_run_calculation, set the column bind::type to int. That tells the survey to treat that question as an integer, allowing your next calculation to correctly add its values instead of concatenating them. ... View more

Kory, If you check out the video Mark uploaded, you'll see he's asking about holding the wheel down until the other pan functionality kicks in, moving in the direction you gesture. This is similar to scrolling a webpage up and down by holding the wheel button. That said, I never understood why the default pan functionality you're showing disables the wheel click while using the Explore tool. It works with all tools in ArcMap, including when Pan tool is active. It's just a weird habit to use one click for 80% of situations, but suddenly switch to a different click for the remaining 20%. The wheel click isn't used for anything else with the Explore tool active, is it? ... View more

Kory, If you check out the video Mark uploaded, you'll see he's asking about holding the wheel down until the other pan functionality kicks in, moving in the direction you gesture. This is similar to scrolling a webpage up and down by holding the wheel button. That said, I never understood why the default pan functionality you're showing disables the wheel click while using the Explore tool. It works with all tools in ArcMap, including when Pan tool is active. It's just a weird habit to use one click for 80% of situations, but suddenly switch to a different click for the remaining 20%. The wheel click isn't used for anything else with the Explore tool active, is it? ... View more

This makes sense--I use Firefox as my default browser. Somehow it managed to update itself this week (I'd been telling it no for months), so even the most current version is still showing this behaviour. ... View more

I can't stress enough how huge a difference this would make. I just had a data layer get corrupted, and now the dashboards that consume it have to be rebuilt from scratch because after fixing the layer, the dashes no longer remember any of the filters or references that had previously been set up. Restoring to/loading a template I had made would have saved me a ton of work. ... View more

This issue still occurs for me in various situations. I haven't done enough testing on my own to figure out the exact set of circumstances that reproduces it (always grouped or also ungrouped? Specific issues in the data? Related tables? Just a random bug?). I did notice, however, that if the data source has a refresh interval set, then the gauges will almost always reset to their correct displays at the first interval after the dashboard is loaded. Any manual refresh of the page itself, though, will have a decent chance of reverting the gauges back to incorrect displays again, and you'll again have to wait for the next refresh interval to fix them. ... View more

Is there a way to get the linked-to web form to honor a query on the repeat records? I followed the steps to embed an editable web form in Operations Dashboard, but ALL repeat records display for any given parent record, and the user has to scroll past all of them to get to the latest record to edit. I'm using the following in bind::esri:parameters, which doesn't seem to be applied in this embedded web form: allowUpdates=true query="${vStatus} != 'Abated'" orderBy=${Date_Inspected} ... View more

I've been forging through what I can and cannot do with related data in Operations Dashboard as well. Here's what I've found out: After publishing a Hosted Feature Service with related table (my workflow is here, but I need to use Survey123, so I don't know how much of that is relevant for other workflows), and adding that data to a web map, both the HFS and related table appear in OpsDash as target layers for various widgets. You can do a decent amount with widgets using the related data, but filtering the map is still not very easy. If you need to use filters based on the zip codes in your delivery data, then something you might want to look into is joining the data. I started a test run of this, but haven't yet had the time to scale it up and determine how useful it will be. I joined the HFS to the table (either this seems backwards to me, or I just don't know what I'm doing), set up a 1:M join based on an Address field in both items (haven't yet checked if I can do this based on the matching GUID/GlobalID noted in my earlier workflow), and created a hosted feature layer view from the join. This cost me 0.3 credits for 300 records (total parent records + total related records). This view has a single point for every related record, which includes the full attributes of the corresponding parent record. This so far seems to work in OpsDash just as much as any other non-related layer does. The big question, however, and I did not get to test this yet, is "Is this view completely static, or will it update whenever I add/modify records in the original HFS/Table? And if it updates, will it cost more credits?" Even if this works for what you're looking to do, I'm sure it's still not an ideal solution. This is as far as I've gotten right now, and maybe it can provide some sort of starting point for you. Of course, the best solution would be for Operations Dashboard to work more fluidly with related data, or, alternatively, for it to honor custom attributes via Arcade (this workflow would directly apply to your situation, and here's a related Idea to upvote). ... View more

I have the same issue, and so far I don't see a way to easily filter the points in the map this way. The closest I've got going myself is to have the chart filter a list widget of the related data, and allow that list to filter (via multiple select) the map. Unfortunately, this is a hassle with small data sets, and completely unworkable with large ones. ... View more

Thanks for the information--I'm looking forward to the future symbology improvements! I've just submitted a bug report as per your suggestion. ... View more

Bumping this question in the hopes that someone has a solution. It's very frustrating how unreadable these symbols are in the legend. The tiny symbols are also what get used in the list widget of Operations Dashboard, further limiting the public-facing options for data symbolized in this way. It happens with any data I try symbolizing by "Types and Size." No matter what options are set for the the size variable, the types--as represented in the legend, not the map--default to 8px in size and seemingly cannot be changed. ... View more