Latest Contributions by NickDierks1

It's no trim, but you could try adding a constraint to prevent survey responses from being submitted with trailing whitespace: not(regex(., '\s$')) The $ within the expression specifically looks for matches at the end of the string. The \s matches any whitespace, including spaces, tabs, and carriage returns (in case you're using this in a multiline text field). Quick Reference: Regular Expressions ... View more

What about using not(regex(., '\n')) in the constraint column? This should prevent anyone from submitting the survey if there are carriage returns in the question(s). Just be sure to add a very clear constraint message! ... View more

Has this feature been removed, or am I missing something? None of my dashboards can be opened from this app. The options I get are Favorite, Share, and View item details. Hosted feature layers and web maps all have "Open in browser" links, but there's nothing like that for dashboards. All my dashboards were made using the web interface, so they shouldn't be legacy/desktop versions. ... View more

It sounds like rather than a hotspot visualization, you'd benefit more by symbolizing your data based on counts and amounts (size or color). Since you said a major obstacle is the high number of points, what if you filtered out the bottom X%, so you showed only higher values? It's not ideal, because your map will no longer show where low spots are, but your 'hotspots' will be clearly identified. Or maybe you could spatial-join your data to counties or something, with each county showing the average values of your chosen attributes? ... View more

This is a really, really good idea. Take the Citizen Problem Dashboard, for example (pre-January 2019 update): Every time I show this to someone, they try clicking on the indicators to go to that data. Looking for the tabs along the bottom is less intuitive, especially when they sometimes coalesce into one large tab with little arrows on the sides (difficult to realize there are multiple tabs there, much less what those tabs are, if you're not familiar with the dashboard). It would be awesome to be able to click on an indicator and go straight to a specified tab (where detailed map and list content would reside), or maybe even have that indicator filter other map(s), list(s), etc. accordingly. Right now, indicators make decent at-a-glance references, but are still sorely underutilized in a well-connected dashboard. ... View more

This is a really, really good idea. Take the Citizen Problem Dashboard, for example (pre-January 2019 update): Every time I show this to someone, they try clicking on the indicators to go to that data. Looking for the tabs along the bottom is less intuitive, especially when they sometimes coalesce into one large tab with little arrows on the sides (difficult to realize there are multiple tabs there, much less what those tabs are, if you're not familiar with the dashboard). It would be awesome to be able to click on an indicator and go straight to a specified tab (where detailed map and list content would reside), or maybe even have that indicator filter other map(s), list(s), etc. accordingly. Right now, indicators make decent at-a-glance references, but are still sorely underutilized in a well-connected dashboard. ... View more

Even if you had to manually upload the config file to each layer, this would still be faster than the current method of reproducing the entire workflow on every single instance. Great idea! ... View more

I just came across another area where ESRI is not at all clear on credit usage: premium maps/data. Take a look at the information page for the US Crime Statistics map, for example. The item's brief description warns that an AGOL subscription is required, but says nothing about credit usage. Without any prior knowledge of what premium content is, one might assume (as I did) that the Premium tag simply referred to that need for a subscription and nothing more. There are exactly two warnings on this page about credits: one in a mouse-over popup on the Premium tag (very easy to miss), and another in very, very small font way at the bottom of the description. Incidentally, the hyperlink embedded in the latter does not actually take you to any description of credit usage--it just makes you log in again (even if you already were), and then drops you back at your organizational account page. Super helpful. Reading through this breakdown of credit usage, it's not immediately clear how a map like this uses credits. My best guess is the line that reads "Demographics and Map Layers: 10 credits per 1,000 map requests (pan, zoom, and identify)" in which case, yikes, just exploring a map like that for more than a few minutes can really start to eat into your credit budget, especially if you don't have a whole lot to start out with. Perhaps a pop-up warning when you click "Open Map" that explains not just the fact that you'll be using credits, but how those credits will be used up is in order. At the very least, maybe a big bold warning in the item's brief description. Because otherwise, it really does feel like ESRI is intentionally obfuscating credit usage in an effort to trick users into spending more credits than they realize. ... View more

This is a pretty interesting idea. Even moreso if your dashboard is setup with category or time filters--gives you your own makeshift "Trending" widget! I like it. The ability to filter out generic words is key, and would be even better if that filter could be customized (in case your data makes certain words more common but you're not interested in adding them to the cloud, such as "species" or "customer" or whatever). ... View more

I haven't explored how it works when your survey is set to multiple pages, but you should be able to make entire groups relevant. Take the relevant clause in line 42 and apply it to that group (line 41) instead, and see if that works out like you're expecting. ... View more

The configuration below is what I'm using to calculate the slopes, and it seems to be working well. I do admit that I'm still somewhat new to utility data, so it's possible I'm overlooking something important, but maybe this will still provide a good jumping-off point? Fields Needed: Manholes: HIGHELEV (elevation of the invert into the manhole) INVERTELEV (elevation of the invert leading out of the manhole) Mains: UPELEV (to be calculated) DOWNELEV (to be calculated) UPFIXED (if the upstream end of the main connects from a different invert than the INVERTELEV recorded in that manhole; useful for manholes that drain in two directions) DOWNFIXED (if the downstream end of the main connects to a different invert than the HIGHELEV recorded in that manhole; useful for manholes with multiple incoming pipes) SLOPE (to be calculated) Rules (in order): Table Name Field Name Value Method Value Info Mains UPELEV FROM_JUNCTION_FIELD INVERTELEV Mains DOWNELEV FROM_JUNCTION_FIELD HIGHELEV Mains UPELEV EXPRESSION UPFIXED Mains DOWNELEV EXPRESSION DOWNFIXED Mains SLOPE EXPRESSION round(((([UPELEV] - [DOWNELEV]) / [SHAPE_Length]) * 100), 2) If UPFIXED/DOWNFIXED are null, then they won't overwrite the previous calculations, resulting in a situation like so: The main gets its UPELEV value from Manhole A's INVERTELEV, and (temporarily) the DOWNELEV from Manhole B's HIGHELEV. But that HIGHELEV is actually recording the elevation of a different pipe flowing into Manhole B (viewed in cross section here). So the elevation of this main's downstream end is recorded in the DOWNFIXED field, which overwrites the previous value (because this rule is applied after the first). Meanwhile, since there's no need for an UPFIXED value, the <Null> doesn't overwrite the initial UPELEV that was calculated. Now just apply the slope calculation, and you're good to go. Hope this helps! ... View more

Adding on to the very helpful resource Mike provided, there's also this tutorial on specifying where geopoints are and aren't allowed to be recorded, which you might find useful: Limiting Extent in which a Point can Exist This would pick up not just on points at 0,0, but also those that fall outside of the area you expect them to be (I once had a user that wound up recording stray points in Siberia, Australia, the Dead Sea, and the middle of the Atlantic, while working in Wyoming!) For your situation, you could set this process up to trigger a relevant question, as you describe, instead of keeping it a constraint. ... View more

I'd like to see this applied to pie charts as well. Right now, their items are ordered from largest to smallest, but sometimes (as in the example you provide) you just need things in a different order. It's very helpful when comparing two such charts with the same items but in different relative percentages. ... View more

I'm not sure what's going on, then--the formulas are working fine in my test so far (see attached xlsx form). Is your username actually 'Internal'? Because what's in those quotes needs to match your username exactly for that formula to work. As for the pulldata(), yes, you can use that as a result in an if/then statement or even in the coalesce() function. You could follow this example and put it where you like: pulldata('ContactList', 'Email', 'UserName', property('username')) The survey I attached uses two of these pulldata() functions within a coalesce() function, pulling the email of either the logged in user or the user selected in ${Call_In_Name}. Try it out, and make sure to save the attached ContactList.csv to the media folder to see it in action. Note that for this to work, the Call_In_Name choices have to match the other usernames exactly, including being case sensitive. If you're still having trouble, try sharing your xlsx form (my email is in my profile if you don't want to attach your survey here). It's possible there's a typo in some formula or other that's throwing things off. ... View more

Sure thing; attached is the test form I used to confirm it wasn't unique to my other survey. ... View more