Latest Contributions by AlexJohnson

‎02-01-2023

Yes, it's definitely possible. (Not always straight-forward, but possible. I've run into several different issues publishing joined tables.) I'd recommend that your joined tables are registered with the geodatabase, as I worked out in this previous thread: https://community.esri.com/t5/arcgis-enterprise-portal-questions/popups-and-joined-geodatabase-views/td-p/1232001

‎12-21-2022

Just wanted to post that I found a solution to this issue: If the joined view is not registered with the geodatabase, the view name is prepended with a '%' sign when joined to a layer in ArcGIS Pro. This can be observed in the 'Layer properties->Joins' window for the joined layer. This causes the '%' sign to be in the fully-qualified field names for those fields in the joined tables, and ultimately results in popups not working for that layer in the web viewer (thought they do work in ArcGIS Pro). Once the view is registered with the geodatbase, the '%' sign is NOT prepended to the view name when joined to a layer in the map. The '%' sign is then NOT in the fully-qualified field names for the joined table fields, and the web map popups work as expected.

‎11-15-2022

We have a third-party application populating a table of manhole inspection records in a SQL Server database (but it's not our enterprise geodatabase). We would like to display this data in a webmap popup in ArcGIS Enterprise. I've created a view of the inspection table in our geodatabase using the Create Database View tool. I can join it to our Manhole featureclass in ArcGIS Pro, symbolize it, and configure popups to display the joined fields. However, when we publish this featureclass with the join to Portal, the webmap popups do not appear. We can symbolize on the joined data and it appears in the attribute table. Clicking for a popup just produces no response. In the server logs I can see an error: An invalid where clause or definition expression has been requested: "stpud.DBO.%vwManholeInspection.Comments,stpud.DBO.%vwManholeInspection.MaxCondition,stpud.DBO.%vwManholeInspection.TestBY,stpud.DBO.sManhole.FacilityID,stpud.DBO.sManhole.OBJECTID,stpud.DBO.sManhole.GlobalID,stpud.DBO.sManhole.Shape" I suspect it's having a problem with the "%" symbol ArcGIS adds to the qualified name of the view, e.g. "%vwManholeInspection.MaxCondition". Interestingly, if I use the webmap popup configuration tool to configure the popup, it will show the joined data in the popup preview just fine. The popup will just never display in normal use. I've opened a support ticket with ESRI, but thought I'd post here as well to see if anyone else has run into this problem. ArcGIS Pro 3.0.1, ArcGIS Enterprise 10.9.1.

‎05-27-2016

Robert - Nice Widget! I'm playing around with it in Web AppBuilder Developer Editing verion 2.0, and get: RequestError: Unable to Load //utility.arcgisonline.com/arcgis/rest/services/Geometry/GeometryServer/project?f=json&outSR=4326&inSR=102642&geometries=%7B%22geometryType%22%3A%22esriGeometryPoint%22%2C%22geometries%22%3A%5B%7B%22x%22%3A7129879.578318954%2C%22y%22%3A2101040.8799832524%2C%22spatialReference%22%3A%7B%22wkid%22%3A102642%2C%22latestWkid%22%3A2226%7D%7D%5D%7D That URL works fine in a browser window, returning the projected geometry. I'm suspect I'm missing something obvious... Ideas?

‎11-08-2011

This problem bit us after our upgrade to SP2 last month. We export 30+ featureclasses from ArcSDE periodically, so we created a Python script and a set of tools to automate the process. At SP1 it took about 15-20 mintues to run. After SP2, it tool over 6 hours. On ESRI's suggestion we updated to SP3, but saw very little change. We worked with ESRI tech support, isolating the problem to the FeatureClass-to-FeatureClass tool. We tested it with a non-geometric network featureclass (~29,000 points) and a geometric network featureclass (~24,000 points). Results were as follows: 10.0 SP3 Non-net featureclass: 17 min 30 sec Net featureclass: 51 min 10 sec 10.0 SP1 Non-net featureclass: 18 sec Net featureclass: 22 sec The geoprocessing output and my notes: SP3 Exports: --Address FC, no geometric network, 29,088 points, 11/4/11 Start Time: Fri Nov 04 13:49:30 2011 Succeeded at Fri Nov 04 14:07:00 2011 (Elapsed Time: 17 minutes 30 seconds) --Ran through the progress bar twice - once really fast, then very slowly. --Sewer Service Connection FC, geometric network, 23,882 points, 11/4/11 Start Time: Fri Nov 04 14:09:48 2011 Succeeded at Fri Nov 04 15:00:58 2011 (Elapsed Time: 51 minutes 10 seconds) --Ran through progress bar at least five times. SP1 Exports: --Address FC, no geometric network, 29,088 points, 11/4/11 Start Time: Fri Nov 04 19:33:55 2011 Succeeded at Fri Nov 04 19:34:13 2011 (Elapsed Time: 18.00 seconds) --Ran through progress bar once, fast. --Sewer Service Connection FC, geometric network, 23,882 points, 11/4/11 Start Time: Fri Nov 04 19:36:25 2011 WARNING 000645: Output format does not support GlobalIDs. Field GlobalID will not be converted to output. Succeeded at Fri Nov 04 19:36:47 2011 (Elapsed Time: 22.00 seconds) --Ran through progress bar once. Obviously, SP3 (and SP2) are causing a big slowdown. One symptom we observed was that at SP2 and SP3, the progress bar in the featureclass-to-featureclass tool would run multiple times. Finally, ESRI was able to duplicate the problem, and they were unable to correct it. Their suggested work-around was to keep on client computer at SP1 for our exports. ESRI tech support logged a bug, if you're interested in tracking it: 'NIM075066: FeatureClassToFeatureClass_conversion performance times are slower'.

‎07-20-2011

I've confirmed this is a version mismatch between the SQL Server Express version used to create the mdf and the version it is being attached to. When trying to attach an mdf file in ArcCatalog, I got the message: The database cannot be opened because it is version 661. This server supports 655 and earlier. A downgrade path is not supported. The mdf was created under SQL Server Express 2008 R2, and the database I was trying to attach to was SQL Server Express 2008. Upgrading the 2008 database to 2008 R2 allowed me to attach the mdf. -Alex ______________________________________________________________ A r e t e S y s t e m s Alexander Johnson, P.E. e-mail: alex@aretesystems.com skype: ax_johnson

Online Status	Offline
Date Last Visited	‎12-01-2023 11:02 PM

My Ideas

Latest Contributions by AlexJohnson

Re: Map service with joined tables

Re: Popups and joined geodatabase views

Popups and joined geodatabase views

Re: Google Street View Widget 2.1 - 08/29/16

Re: Feature Class to Feature Class tool extremely slow Arc10 SP2

Re: the database cannot be opened because it is version 655.

Re: Popups and joined geodatabase views