Latest Contributions by NickDierks1

‎04-29-2019

It sounds like the suggestion isn't about simply being able to create a featureless record by accident, but more about how much easier it is in Pro than in ArcMap. In Pro, a single click on that bottom line in the table and boom, new record, no geometry, ready to go. In ArcMap, a single click on the bottom line of the table doesn't do anything. It takes a double-click, or an overzealous copy-paste mixup to add a new record without a feature. I don't see anything in ArcMap where a single click from a standard interface can create a featureless record, but in Pro, as long as you have the attribute table open, you can. This is very similar to this idea about the Delete Field button. An accidental click in the wrong place can result in a potentially major disruption. It'd be like having your car's "pop the hood" button right next to your radio controls. Not something you want to accidentally press while cruising down the highway!

‎04-29-2019

By my count, geocoding via ArcMap has been adding 31 fields to my schema. That's more than is in most of my datasets! And all of them come before my actual data. My workaround has been to geocode into a temporary feature class and then append that to the master feature class. But then again, none of my own fields were renamed in the process, so field mapping has been pretty simple. But I'm definitely all for bypassing those extra fields to begin with. I only kept a couple (which locator was used, and how the point was matched/mapped), but I can easily live without them.

‎04-26-2019

Cada casa es una encuesta separada, ¿correcto? Si es así, no creo que haya una manera de abrir automáticamente otra encuesta específica después de enviar una. ¿Está actualizando los datos existentes? En otras palabras, ¿cada casa ya es un punto en el servicio de características antes de comenzar a leer los medidores? Si ese es el caso, su mejor método es probablemente usar la Bandeja de entrada. Al acceder al mapa de la Bandeja de entrada, puede ver cuáles están cerca, lo que es lo más cercano a completar encuestas secuenciales. Consulte esta documentación para obtener más información sobre el uso de la Bandeja de entrada: Preparar la edición datos existentes de la encuesta—Survey123 for ArcGIS | ArcGIS (Traducido con el Traductor de Google; me disculpo si no estoy muy claro)

‎04-25-2019

This should definitely be doable--I've got that setup working on multiple dashboards. I know one goof I constantly make is that I'll add a widget to the actions of a selector, but then forget to set the target field, which means my addition doesn't get saved and the selector won't filter that widget. If you're not making that same mistake I do, could you describe what happens in step-by-step detail? Do you add the list to one selector, then go to the next selector and the list isn't available to add? Or can you add it to both selectors, but only one of the selectors actively filters it? If so, is it always the same selector that works?

‎04-25-2019

I've got a layer of code violations with several date fields. Many of these date fields are used successfully in indicator and chart filters, as well as filtered correctly with a date selector in the header of the dashboard. One date field, however, is treated as a Coded String in all widget filters except for the date selector in the header, preventing me from using any meaningful date filtering using that field. This field is correctly formatted as a date in the original desktop layer and the hosted feature service. What could be causing this?

Dashboard User Preferences · ‎04-23-2019

It would be great to somehow implement user preferences for dashboards, so that a logged-in user can 'save' a dashboard with their own customized view of displays, widgets, and so on. Things like: Dark vs Light theme Which tabbed widgets are open by default What basemap is used in the map widget(s) What layers are on/off in the map widget(s) Maybe even which category selections are active by default That way, User-A can open the dashboard with a dark theme, Dark Grey Canvas basemap, and Firefly-symbolized layer, while user-B opens the same dashboard to an imagery basemap using a heatmap-symbolized layer, and User-C opens the dashboard directly to the tab of pie and bar charts. All of these options would be built in by the dashboard designer just like in any other dashboard, the only difference is that users can choose what elements are visible/enabled by default when they open it. This would allow dashboards to be that much more versatile when they have multiple different end-users, reducing the necessary number of clicks on their end to get to the data/visualization they want to see. Currently, the only way to approximate this setup is to maintain multiple different dashboards, each catered specifically to a different user's preferences.

‎04-08-2019

It doesn't look like you can put If statements within a group name, so changing the text colour dynamically probably isn't possible. One workaround you can try is to use note fields that come after each group. Using the string-length() function, you can easily determine if a given question is answered or not. For example, writing string-length(${question})>0 in the relevant column will make a note or other question appear only when the referenced question has text entered or a choice selected. I'm attaching a form that uses two methods of recording this and displaying it with note fields. One method is a simple "all answered" vs "all unanswered" relevancy. The other method will actually display the number of answered questions as the user fills out the group. Take a look and see if either method may help you with what you're looking for.

‎04-08-2019

Web forms don't seem to treat field lengths the same way the field app does. The field will turn red, indicating an invalid input, but it's the user's responsibility to trim back the text entered. The survey still can't be submitted with extra characters in that question. I did notice a related issue with field length: If your survey was originally published with a longer field length (255 by default if none set), then republishing with a shorter field length in that same question won't change what you can submit. You can still submit up to 255 (or whatever the original length was). The regex formula will still help with that, as it will only accept a phone number in the format of XXX-XXX-XXXX, no more, no less. But again, nothing is going to physically stop the user from entering an invalid format or length until they try to submit. That said, your form does need a couple changes if you're going to use that regex formula. The required field length is 12 characters, not 10 (the dashes are counted), and the input mask--while not currently honored in the web form--will interfere with validating the regex formula as written if using the field app (XXX-XXX-XXXX vs (XXX) XXX-XXXX).

‎04-05-2019

Unless someone else knows of a workaround, I think you might be. There are currently some enhancement requests for supporting Arcade expressions in Operations Dashboard, which might be able to get the job done depending on how that's implemented, but that's still not a reality yet. Otherwise, reworking your survey to avoid using a select_multiple, or adding a bunch of hidden fields (monday_yesno, tuesday_yesno, etc.) may be your only options for recreating that graph in Ops Dashboard.

‎04-05-2019

Input masks do not currently work in the web form. Regular expressions should work fine, though. I just tested your first regex example, and I got it to work in the web form when used as the constraint on a text field (consider altering the expression to regex(.,'^[2-9]\d{2}-\d{3}-\d{4}$') to make sure only a matching phone number will be accepted). If this doesn't work for your survey, would you be able to share your survey or provide more details on how it's not working?

‎04-05-2019

Is that question a select_multiple? If so, I don't think Operations Dashboard is able to parse out the individual choices within each survey response.

‎03-28-2019

Thanks for the response--good to know it'll get looked into. And that's definitely a much simpler workaround than my note method--can't believe I spaced and forgot about using a constraint!

‎03-26-2019

I love that character counts automatically display in text fields now, but I noticed that in web forms, they only do so outside of a repeat. For web form text fields in a repeat, no character counts are displayed and--more importantly--field length isn't enforced. A user can enter in much more than the allowed length with no indication that it's incorrect. When submitting the form, a generic error appears stating "Failed to Submit: Operation rolled back. String or binary data would be truncated. The statement has been terminated" without indicating which question in particular caused the error. While I found some discussion of the above error in different contexts, I couldn't find anything on this particular situation when I searched GeoNet, so I wanted to check if it's a known issue, and if it's being worked on at all. It looks like it works just fine in the field app, so that's good at least. Fortunately, in the meantime for anyone else who might run into this, workarounds are simple enough using string-length(): For Display remaining character count: use concat(string-length(${example}), ' of 500') in the calculation of a note field. For helping warn users who still managed to go over the limit, just use another note field with string-length(${example})>500 in the relevant column. This ought to give a user a heads up before they try submitting the survey.

‎03-25-2019

I don't see any way to do it with an indicator, but you could go with the much less fancy route of using a filtered list widget. Set the filter to Today (it's a shame you can't filter to "Within the last/next X days"), and change the line item text to something like "Today's Sunrise: {sunrise time}" That said, displaying non-numeric data via an indicator (or other new widget?) or even a clock-style widget specifically for time would be an excellent enhancement request.

‎03-19-2019

Using regex is definitely the way to go. As I posted in a similar thread, you can use the following expression in the constraint column: not(regex(., '\n')) I've tested this a bit in another survey and it seems to work well at preventing any line breaks. Just make sure you provide a descriptive constraint message so that users understand what's going on.

Online Status	Offline
Date Last Visited	‎03-26-2021 12:04 AM

My Ideas

Latest Contributions by NickDierks1

Re: Remove 'Click to add new row' from feature class attribute table

Re: Add possibility to remove all "Match" columns when geocoding from ArcGIS Pro and ArcMap

Re: Toma de lecturas

Re: Using Date Selector and Category Selector at the same time?

Date field treated as Coded String in filter menu

Dashboard User Preferences

Re: Is it possible to change text color based on certain conditions?

Re: Limiting the characters for a Phone Number

Re: Survey Results in Operations Dashboard?

Re: Limiting the characters for a Phone Number

Re: Survey Results in Operations Dashboard?

Re: Web Form Repeats: Character Counts and Field Lengths

Web Form Repeats: Character Counts and Field Lengths

Re: Indicator in Operations Dashboard

Re: Constraint: No Line Feed

Re: Survey Results in Operations Dashboard?

Web Form Repeats: Character Counts and Field Lengt...

Re: Geofence Survey123

Re: Remove all empty spaces at the end of the text

Changes to time zone info? (Appending to feature s...