Latest Contributions by BrianFausel

Sure you're welcome. Indeed, there is no real good way to "hide" the Near Me widget - it has to be docked like I have it or it has to be an optional tool that a user can click from the toolbar. FYI: It is possible to show all parcels and not just the selected one. See attached pic, its an option in the Near Me configuration called "Only draw selected layer results." If unchecked: all the parcels show. ... View more

Voted up. Its frustrating that this functionality is available in some apps but can't be as easily achieved in WAB. I have a partial workaround in this similar Idea thread involving the "Near Me" widget. ... View more

I figured out a workaround for this, but yes it would be nice if the related table info from 1:M could be displayed directly in the popups without the current "drilldown" method. I definitely voted UP for this idea. In the meantime, here's my workaround: Use the standard WAB widget "Near Me." Configure it for a single layer and limit the number of results to 1 in the search settings. When you set it up to search a Feature Class (1) : Related Table (M), the related records will show up at the bottom of the "Near Me" report. You can control the attributes that appear in the report in the web map popup area. Here's a link to the app that I am working on if you want to see it in action. It's a basic parcel viewer that shows parcel info/tax total (1) : payments made (M). Commercial and industrial properties are the ones that typically have 1:M examples (you can zoom+click the parcel to see the "Near Me" info without searching). The only drawback to this workaround is I don't think you can set the order of the entries coming from the :M table. The database is pretty simple. Parcel feature class (1) : Tax payment table (M). Was created using ArcGIS in a file geodatabase with relationship class. Published to ArcGIS Online as a feature service. ... View more

Darren's response was the answer to my dilemma. After seeing the error "Cannot Access Data" with my spatial view, I was finally able to get the new "web-based" Op Dashboard to work by using OBJECTIDs. This works even with our legacy ArcGIS Server 10.3.1 / SQL 2008 R2 environment. I'll try to sum it up as best I can: The key seems to be to use the OBJECTID attribute rather than the GLOBALID when you define the unique identifier in ArcMap. I have a pretty simple 1:M relationship modeling Hydrants(1):Events(M). The relationship class keys are Hydrant(GLOBALID):Event(GUID). Both the feature class and event table are in the same SDE geodatabase. When adding the spatial view to ArcMap to create an ArcGIS Server map service, I was originally using the Event GLOBALID as the unique identifier. While the Event GLOBALID is unique, any time you add the service to the Op Dashboard it would give the message "Cannot Access Data." From there you couldn't create pie or serial charts. SOLUTION: I re-created the map service using the Event OBJECTID as the identifier and now it works great with the Op Dashboard as well as the Web AppBuilder Infographic widgets. Sidenote: The thing that was driving me most crazy was that I had other more complicated spatial views that were working the whole time while this new one was not. The other spatial views involved an SDE feature class and multiple business tables from an external asset management database. In that case, I was using the OIDs of the external database. So I can vouch that it also works outside SDE, provided you have that unique identifier. ... View more

Thanks for checking the code Robert. I have switched my strategy a bit and am now testing the real "Operations Dashboard" as opposed to the WAB "Dashboard." In there you can set the Infographics (pie and serial) to interact with a date range picker. ... View more

Thanks for the update, Laura. Sounds like your scenario is the exact same as ours: "Edge can hit the rest service page, display any service using the Javascript viewer, but cannot display any service using the ArcGIS online viewer... This is our internal server, not configured with HTTPS, or web adapter." ... View more

Hi Derek, We had a support case open and since closed as well (#02094066). We tried a variety of things and were not able to nail anything down. The case was left with a question for our IT to see if there was any device on the network that might be caching requests between the internal Edge browser and the ArcGIS Server. IT is not aware of any device doing that, though he was not able to rule out the firewall as a possible problematic source. We'd be happy to be a test site for the support crew working on the bugs if needed. ... View more

Our organization is also experiencing this problem. The AGOL-hosted web apps that are consuming local (on-premise) ArcGIS Enterprise REST map services have these testing results: Do NOT work in Edge when viewed in-network on-premise. The AGOL-hosted content and app buttons show up, but the Enterprise map services do not. DO work in all other browsers tested (Chrome, Firefox, IE) when viewed in-network on-premise. DO work in all browsers, including Edge, when viewed outside of our network. Do NOT work in Edge when viewed outside of our network while on a MS VPN. The AGOL-hosted content and app buttons show up, but the Enterprise map services do not. I have worked with both Esri Support and our IT Department and haven't been able to determine where the fix is. I have a *theory* it could be related to mixed content / mixed security. Our Enterprise REST map services are HTTP (currently), while the AGOL web map and Esri-hosted data is HTTPS. But again, I haven't been able to get to the bottom of this. In the meantime, we have instructed our users not to use Edge. ... View more

In the case I encountered here, I added a hosted feature layer (initially not set to be editable) to a web map. Then, I changed the hosted feature layer settings to be editable. After doing that, the web map still did not show up in Collector. I found this thread, so then I went back into the web map and simply did a Save. Then, the web map showed up in Collector. Another (slightly unrelated) thing you might have to do is share the web map with an AGOL group that includes the Collector user in the group. Having a web map that is stored in AGOL but not shared with a group will result in it not showing in Collector. ... View more

This is still a thing in Spring 2018, and Miaogeng's solution was the fix for me as well. ... View more

For what it's worth, here are some observations possibly related to this issue that I had in our antique and unsupported environment: SQL Server 2008 R2 geodatabase is not supported in ArcGIS Pro, but one can add LYR files with pointers to SQL 2008 feature classes and they show up and work in Pro version 2.0 and earlier. Starting in Pro 2.1 and also in 2.1.2, these LYR files stopped working (layers appear with red exclamation point and claim invalid data source). Our LYR files were originally created using a database-authenticated connection, connecting through a generic "GIS_User" login. It's a bad legacy design we are planning to move away from. If I create a new LYR file with OS-authenticated login connection using ArcMap, this LYR file does indeed come in without issues into Pro version 2.1.2. In this case, I didn't even have to explicitly grant permissions to my login on each feature class. We are not affected by this problem in ArcMap versions 10.2.2 or 10.3.1 and have not yet upgraded to 10.5.1 or higher. We also do not have general users in Pro yet -- we are waiting until the database can be upgraded to a supported version before rolling it out. ... View more

Sure. I wasn't even aware of the subtype issue, but I can see that being a major problem. I'll see if I can add it to my Idea because it is definitely related. When I was viewing your thread I noticed another similar thread that had a workaround for subtypes (symbolize using them), but it may not work for your case. ... View more