Latest Contributions by Amanda__Huber

Hi Kory,  Good to know that the quick access toolbar is different than the ribbon tabs. I was unable to find any documentation when searching for how to set up this Quick Access Toolbar. Is there any chance you could pass on the setup information to me? Thanks,  Amanda ... View more

Hi Kory, That's a great alternative! I've dabbled with moving around tools in the banners before, but it seems those settings only stay for that specific project. If you're working across multiple projects, you would have to set these each up that way (which isn't the worst, just one more step). I will use this workaround for now since we use definition queries quite a bit here at the Park District. But it would be really nice if there a was an out of the box option for this.  Thanks so much! - Amanda ... View more

Hi Scott,  Thank's so much for responding to my post! I have been able to mimic some of the cascading capabilities through smart editor by setting up rules based on answers, but as I mentioned before it's very difficult to do. In addition since smart editor Ideally, the power of  a XLS form and its capability would be great and would allow the user to continue to use S123. My conceptualization is to keep S123 and WAB as separate products but have the capability to embed a S123 into widget (like an iframe) or (even better) have a Survey 123 Widget that you can point to one of your published surveys. Please see mock-up below.  To be honest, There doesn't seem to be a option for editing related records that  also has a good user interface in AGOL as a whole much less in WAB. In the mentioned above smart editor widget, we have to use Geoevent automation to push the data from the input parent table to the related child table and then clear these fields for the next observation. This is something that S123 does effortlessly. We are actually using S123 with an existing feature service. In one of our other WAB applications we are using S123 as a hyperlink which passes attributes from the parent table point clicked on to the related child table via the in the URL syntax. This works great, but the problem is when users (typically and older generation of volunteers) click on this hyperlink on a mobile device it navigates them away from the WAB to a new tab. This can be confusing for users, if they don't know how to return to the WAB to complete more observations. Ideally a all in one S123 and WAB in one would be great. No navigating away from the app, and a streamlined observation process for users (with a robust XLS form capabilities in the back end).  If you're interested or would like to see how we're using these technologies first hand, I would be more than happy to set up a screen share meeting with you.  Concept art for S123 Widget in WAB:  Thanks again so much for your time,  Amanda Huber ... View more

Hi Scott,  Thank's so much for responding to my post! I have been able to mimic some of the cascading capabilities through smart editor by setting up rules based on answers, but as I mentioned before it's very difficult to do. In addition since smart editor Ideally, the power of  a XLS form and its capability would be great and would allow the user to continue to use S123. My conceptualization is to keep S123 and WAB as separate products but have the capability to embed a S123 into widget (like an iframe) or (even better) have a Survey 123 Widget that you can point to one of your published surveys. Please see mock-up below.  To be honest, There doesn't seem to be a option for editing related records that  also has a good user interface in AGOL as a whole much less in WAB. In the mentioned above smart editor widget, we have to use Geoevent automation to push the data from the input parent table to the related child table and then clear these fields for the next observation. This is something that S123 does effortlessly. We are actually using S123 with an existing feature service. In one of our other WAB applications we are using S123 as a hyperlink which passes attributes from the parent table point clicked on to the related child table via the in the URL syntax. This works great, but the problem is when users (typically and older generation of volunteers) click on this hyperlink on a mobile device it navigates them away from the WAB to a new tab. This can be confusing for users, if they don't know how to return to the WAB to complete more observations. Ideally a all in one S123 and WAB in one would be great. No navigating away from the app, and a streamlined observation process for users (with a robust XLS form capabilities in the back end).  If you're interested or would like to see how we're using these technologies first hand, I would be more than happy to set up a screen share meeting with you.  Concept art for S123 Widget in WAB:  Thanks again so much for your time,  Amanda Huber ... View more

Hi Kai,  That is very peculiar behavior. We haven't had any fluctuation in behavior on our end but it definitely sounds very similar to our issue.  ... View more

Hi Brian,  That's a good theory and could be part of the issue for your organization. The only catch is, our REST map services are HTTPS and we are still experiencing this issue.  ... View more

Hi Derek,  Thanks so much for the response!  Unfortunately we have already opened a case with support and since closed it since they mentioned they were unable to assist us since it's an 'internal issue' (Case # 02107067). This is why we turned to GeoNet to see if any other organizations may also be experiencing this issue, and if they resolved it.  As it seems from the above threads, we are not the only organization facing currently facing this issue. In addition, you're in luck our dashboard is publicly accessible. Here's the link: Operations Dashboard for ArcGIS  Thanks,  Amanda ... View more

Hi Bill,  I'm so sorry to hear you are experiencing this same issue. We're seeing that exact same behavior, but we have still not discovered the cause or a solution. Our IT team has been looking deeper into the behavior but we haven't had much progress. I'll keep this thread updated if we do discover the solution.  Best,  Amanda ... View more

Hi Joe,  Thanks so much your suggestion! I am currently using that technique as my workaround in my WAB app.  That's actually what gave me the idea to make this post, there's gotta be a better way. The url technique does work well, don't get me wrong, but any time a user has to navigate away from the app it leads to another potential point of failure. It's great that the URL opens in a new tab by default, but depending on the audience/users it could be a bit cumbersome or confusing. If the user doesn't realize that a new tab was opened they may not know how to return back to the app.  That's why I propose to keep it all in the same browser window. The Smart Editor Widget has similar capabilities, the ability to Hide, Require, Disable Fields using expressions to ultimately create a cascading form, but it's a lot more difficult to build and is a much less robust form than Survey 123. If there could be a Survey 123 Widget that could point to an existing/newly created survey in your organization that's based of an existing feature, it would be great! It would be mobile friendly and have the best of both worlds!  ... View more

Hi Joe,  Thanks so much your suggestion! I am currently using that technique as my workaround in my WAB app.  That's actually what gave me the idea to make this post, there's gotta be a better way. The url technique does work well, don't get me wrong, but any time a user has to navigate away from the app it leads to another potential point of failure. It's great that the URL opens in a new tab by default, but depending on the audience/users it could be a bit cumbersome or confusing. If the user doesn't realize that a new tab was opened they may not know how to return back to the app.  That's why I propose to keep it all in the same browser window. The Smart Editor Widget has similar capabilities, the ability to Hide, Require, Disable Fields using expressions to ultimately create a cascading form, but it's a lot more difficult to build and is a much less robust form than Survey 123. If there could be a Survey 123 Widget that could point to an existing/newly created survey in your organization that's based of an existing feature, it would be great! It would be mobile friendly and have the best of both worlds!  ... View more