Latest Contributions by LanceCole

@jschuckert, After working with ESRI support on this issue throughout the week, it has been determined this is a BUG-000164046 when working with map services.  There are a few workarounds: Utilize Map Viewer Classic to configure pop-ups. Add the individual feature layers of the map service to Map Viewer <serviceURL>/MapServer/0 rather than <serviceURL>/MapServer. Publish as a hosted feature layer and manage layer properties in Map Viewer. If the pop-ups have not been enabled in the map service, they will not display in FieldMaps; however, once enabled in the map, they will always be on in FieldMaps and cannot be turned off despite the map settings.  You can remove and reload the original services in the map but lose any other configurations. ... View more

@jschuckert , Happy Holidays. So far, I have only been able to turn off pop-ups in field maps by using the Map Viewer Classic.  I also do not see the option to disconnect layer properties for the problematic features as others have noted. I have a support ticket in with ESRI; however, because of the extended holiday we have yet to schedule a phone call and screen share to discuss the issue in more detail.  I will post more once I have more info.   ... View more

Has anyone heard of a permanent resolution or is there an official BUG ID for this?  Using Map Viewer Classic is starting to result in a loss of functionality and an inability to leverage the new Map Viewer in FieldMaps.  Also, I am not seeing the referenced "disconnect layer properties" under the Layer > Properties > Info, as noted in @ajevans429' s post.  We are using Map Services so may account for the missing option. ... View more

@LeslieUK, That appears to have worked.  IT reported Windows was showing the driver as current but a newer driver suite was available from the graphics card vendor.  Updated and the issue appears to have been resolved.  Thanks ... View more

@DominicRobergeIADOT  As @DanPatterson  pointed out above - A good 'google' would show that WGS 1984 Web Mercator (auxiliary sphere) should not be used for feature  creation or analysis but display only.  It is useless for distance or area calculations.   ... View more

@DominicRobergeIADOT  Just keep all you data in a coordinate system that works for you.  Even the data that you publish to AGOL.  You had noted you were using USA Contiguous Equidistant Conic (PCS).  Set your ArcGIS Pro maps to this coordinate systems, when you publish feature or map services, keep this coordinate system.  When you create a map in AGOL, it will be WGS 1984 Web Mercator (auxiliary sphere); however, when you add your data AGOL will apply the appropriate transformation. ... View more

@rmcooper_wcpss,  The License Manager can be installed on any system your portal has access to within your domain.  The overhead is very low and is only hit when a user needs a license.  A dedicated server would be overkill.  We also have a multi-server deployment and have the License Manager installed on our GIS file server hosting all our imagery and files.  We had originally installed it on the Portal itself but later moved it to the file server which has a lower load. ... View more

Thanks, Typo on my part.  Corrected. ... View more

Take a look at these videos: https://www.youtube.com/watch?v=wvLlzqa1-BA https://www.youtube.com/watch?v=lMl4hTX8rGs ... View more

Look at your source data.  Most state plane data is based upon a NAD83 or NAD83(2011), hence my recommendation to utilize one of those.  The USA Contiguous Equidistant Conic (PCS) you noted is also based upon NAD83 and covers USA-CONUS - onshore but uses an equidistant conic projection rather than a geographic coordinate system. ... View more

@vijaybadugu,  I can emphasize your struggles.   You will want to place the IIS server in your DMZ along with both of your web adapters.  The web adapters will serve as a reverse proxy forwarding portal.external.com to portalserver.internal.domain:7443.  This does require the 443 to be open on your external firewall and 7443 to be open on your internal firewall.   A split DNS is required where your portal.external.com IP is sent to your DMZ IIS IP via a NAT through your external firewall and internal DNS is sent directly to your DMZ IP for portal.external.com.  Please keep in mind all traffic for your portal web adapter can only utilize one URL - portal.external.com for both internal and external usage. You will also need a public verifiable CA certificate for your external domain that will be used for your portal.  For example - portal.external.com.  If you have an internal CA you will need to add the authentication roots to the ArcGIS portal and server.  Alternatively, you can copy the self-signed certificates to each system. One configuration change is needed in Portal Administrator Directory.  Navigate to Home > System > Properties and set {“WebContextURL”:”https://portal.external.com/portal”} There is a video on YouTube detailing this process but I cannot find the link at the moment. I highly recommend reaching out to ESRI Support, they have a great team and are very helpful. ... View more

@DominicRobergeIADOT, I am able to replicate what you are seeing by adding parcel data from a NAD83 State Plane System to Imagery in WGS84.  Even with the correct transformations, a 150-foot parcel line is reported as 200 feet in WGS84 and 150 feet in NAD83.  It is not the difference between planner and geodesic as they should be nearly the same for this distance.  Also, geodesic should be larger than planar.  @DanPatterson, care to put your professor hat on again and educate us? Try using Geographic Coordinate System > North America > NAD83 (WKID:4269) or NAD83(2011) (WKID:6318) depending upon your prevalent source data.  Both of these cover USA - CONUS. ... View more