Latest Contributions by BrianFausel

When exporting a hosted feature service from ArcGIS Online (AGOL) to a File Geodatabase (GDB), some of the key GDB settings that you originally set up are lost in the export. I have encountered this when feature services were originally created via ArcMap "Share as a Service" from a File GDB.  Please fix the AGOL export so that all of the original GDB settings are preserved in the downloaded File GDB. Specific examples of settings that are lost: 1)  "Default Values" for all attributes of the feature class and related tables 2)  GDB "Domain Description" text 3)  Feature class that you export has a different name in the download GDB than it was in the original GDB 4)  Relationship Class(es) have different name(s) in the download GDB than in the original GDB 5)  Relationship Class "Notification" and "Label" settings are removed 6)  Subtypes ... View more

I have found some very useful solutions to change MXD data sources using python.  The question: Is it possible to automatically switch MXD data sources to an AGO-hosted feature service?  It seems that the replaceDataSource() method would work, but there does not appear to be a workspace_type for AGO. The added challenge here is that the feature class names change - the original file GDB uses the full name (i.e. "Major_Employers") and on AGO the name becomes the number for the REST service (i.e. "0"). I tried modifying the python example "A feature class is renamed" from the Esri help document and it didn't work.  Before I move forward with troubleshooting this code, my main question is can this be done in the first place? Note: I modified the AGO URL in my code example below to remove specifics: import arcpy mxd = arcpy.mapping.MapDocument(r"C:\temp\MXD_Update\Data_Source_Update.mxd") for lyr in arcpy.mapping.ListLayers(mxd):     if lyr.supports("DATASOURCE"):         if lyr.dataSource == r"C:\temp\MXD_Update\AGO_Sync_Testing.gdb\Major_Employers":             lyr.replaceDataSource(r"http://services2.arcgis.com/[url]/ArcGIS/rest/services/[featureservicename]/FeatureServer", "NONE", "0")             lyr.name = "0" mxd.saveACopy(r"C:\temp\MXD_Update\Data_Source_Update_AGO.mxd") del mxd ... View more

I have been using Robert's Identify Widget v 3.6.5 in our Flex 3.6 apps perfectly for about a year now -- great tool Robert, thanks for the support and development of it!  I recently upgraded ArcGIS Server from 10.2.2 to 10.3.1 and encountered a minor problem with the Identify Widget after the upgrade.  I did find a workaround, so this is more of a discussion than a question. We have a map service that contains a feature class from SDE with a join (defined in the MXD) to an external table in another database - both SQL 2008 R2 databases.  This "join" map service worked fine prior to the upgrade to Server 10.3.1.  After the upgrade, the Identify Widget stopped working and throws the error seen in the attached picture when you click on the "join" feature class.  Feature classes that do not have joins still work fine.  The regular Identify tool in ArcMap also still works. I took a look at the newer version release notes for Identify Widget and it does not appear that this issue has been mentioned.  I don't know if this problem is present in versions beyond 3.6.5. Workaround = If I create a spatial view in SDE (including both the feature class and external business table) using ArcCatalog, the Identify works like it did before on the view.  All I had to do was change the <field name> references in the XML configuration to the new "spatial view" map service names. Interestingly the eSearch Widget is not affected by this problem, it still works even with the "join" map service. ... View more