Latest Contributions by AmyRoust

I didn’t try that since the colon wasn’t really critical to the message. I just changed the wording to remove it. I bet you could put an escape character in, though. Would be worth a test if someone absolutely had to have a special character in that spot. ... View more

That did the trick. I had to delete this block of code:      {         "uri": "widgets/Splash/Widget",         "position": {           "relativeTo": "browser"         },         "version": "2.5",         "id": "widgets_Splash_Widget_49",         "name": "Splash",         "label": "Important: Offline notice for server upgrade",         "config": "configs/Splash/config_Important: Offline notice for server upgrade.json",         "visible": false       }, I have a ticket in with Esri support. Hopefully we can get to the bottom of this because I would like to have a splash screen. Plus, I really don't want to have to manually delete a block of code every time I update the website. ... View more

Yes. Here's what I see (blacked out the server name on the URL -- this is on my test server and not live): And since that graphic nearly impossible to read: GET XHR http://[servernameremoved]/propertyviewertesting/configs/Splash/config_Important%3A%20Offline%20notice%20for%20server%20upgrade.json [HTTP/1.1 404 Not Found 11ms] SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data Stack trace: json@https://js.arcgis.com/3.21/init.js:147:461 p@https://js.arcgis.com/3.21/init.js:146:137 f@https://js.arcgis.com/3.21/init.js:138:503 g@https://js.arcgis.com/3.21/init.js:143:291 It is not insignificant that there is an error on the Splash config because in WABDE, I removed that widget before I downloaded the code package. I wonder if there is an error with the Splash widget in version 2.5 that is leaving residual code when it is added and then removed? ... View more

Just tried that at your suggestion, and it came back valid. ... View more

Oh cool, thanks! We’re looking forward to taking it for a spin in our test environment when it’s ready. ... View more

Hi Robert! I just upgraded to WABDE v. 2.5 and downloaded this widget this morning. I'm having an issue when trying to configure the "Update Expression" settings. When I click on the pencil to edit the expression value, nothing happens. It looks like the search by value tab will not appear unless this is configured. Is there a bug? Or, more likely, did I do something wrong with the install? ... View more

That's what I ended up doing with our VRP. Thanks for the help! ... View more

Can you elaborate on which file you placed the HTML code into to make the hyperlinks a different color? The HTML source toggle button in the widget's configure dialogue box is worthless - none of the changes that I make in there will save. ... View more

Thank you for this information! I downloaded our data as a file geodatabase as suggested, which provides the coded results. Unfortunately, the field names change to field_1, field_2, field_3, etc, so we trade one problem for another one. To be fair, I totally understand why the field names have to be converted, since a geodatabase would not accept field names with spaces, special characters, etc. Since this limitation is on your radar, do you have a timeline for when it will be fixed? ... View more

Here are some screen shots from our setup that are creating the same issue. There is no spatial element to ours -- we're just using Survey123 to collect table data. Form design: Data entered: Excel spreadsheet download: Edited to add: I tried downloading in Firefox 53, IE 11, and Chrome 59. Same results from all three browsers. ... View more

The locals are in LOVE with this widget! Thanks, Robert. It's great to finally get all of our historical imagery out for everyone to enjoy. An enhancement suggestion for your next round: the icons for each basemap jump around when you select a different vintage. This confuses people at first because they are expected everything to stay in the same place. A couple of screen shots to illustrate: First opens as this: When I switch to 1954, I get this: In the second example, all of the images slide one slot up. For example, 1966 goes from the second position to the first position. The end user who wants to go through each year instinctively goes to the second position, then the third, etc. Some people figure out what's going on; others get confused when things don't change as they expect. My thought is that the list of options could stay the same, regardless of which image was highlighted at the top. Also, it's a little odd to have the default basemap show up in the list twice when it's not activated. Just something to consider for a future iteration. We are happy people here in NE Kansas. ... View more

Found a workaround. I removed the widget, went into AGOL and changed the thumbnail for each of the basemaps, and then re-added the widget. ... View more