Latest Contributions by JimmyKnowles

@Anonymous User  - the last time we needed to do this, we still needed to manually update the layer definition to be able to take join layers offline. That was back in May, but I don't think anything has changed since then. It worked with Field Maps, but will return errors when you try and sync. Despite the errors saying that the sync failed, all other layers should sync fine. The actual json that you need to update is in Khaled's response... https://community.esri.com/t5/arcgis-online-questions/overwrite-a-feature-service-used-in-join-features/m-p/40896/highlight/true#M1968   ... View more

Thanks for the solution on this, setting 'sanitize_columns' to 'False' worked for me. Certainly doesn't make sense to me since it first modifies the dataframe and not just the feature class that is being written to. Took me a little while to figure out what was changing the case of my field names. ... View more

@DougMorgenthaler thanks a lot. We'll explore that route. And that certainly makes sense having that control at the map level. FYI, that link isn't working for me. ... View more

Any reason why filter related types was removed in this release? This just forced us to move back to Collector for ongoing field work. ... View more

Hi Brenna, I just encountered this error for the first time. Did you ever find a solution to your problem? The only thing I might be able to add is that the fgdb that I received was from somebody using a Mac. Not sure if that has anything to do with the issue, but figured I'd mention it. Thanks, Jimmy ... View more

That works even better @KoryKramer. I thought I tried that, but obviously I didn't or wasn't paying close enough attention. Thanks @Scott_Harris for the better way of doing this. I think I learned enough new things for a Friday 🙂 ... View more

@KoryKramer - that's exactly what I was looking for. Thank you! And now I realize this works in any 'list' in Pro (i.e. contents pane, catalog view, etc.). Hope you're doing well! ... View more

I know it's been several months since your post, but maybe this will help you or others that are in a similar situation. I also had a need for rasterio which uses GDAL and ran into the same dll load failed error. Installing from wheels worked for me. I know it's not best practice to mix conda w/ pip, but I haven't experienced any issues. I followed the instructions from the rasterio page rasterio · PyPI. Wheels can be found at Python Extension Packages for Windows - Christoph Gohlke. Once rasterio and gdal were installed using the wheels, I was able to import both arcpy and rasterio without any issues. I haven't tried geopandas, but I imagine it would work since the problem seemed to be with gdal. ... View more

I can't help with your question, but anyone know why that blog post disappeared and can only be accessed with a password? Wanted to dig into feature service webhooks after reading the blog post, but now can't view it. ... View more

Just wanted to let folks know that we found what was causing the issue for us while working with Esri support. We had 'Optimize Layer Drawing' enabled for the layer in question. Once this was disabled, method=vertex worked. We'll let you know if a bug gets filed for this behavior. UPDATE: This was attached to existing BUG-000127298 for our support case. ... View more

Thanks Bert. You're right. I did some additional testing and this appears to be the culprit, but it is not fixed in 2.5.1. I'll see what Esri support says. ... View more

I'm having the same issue. Here are the steps that I take to recreate the issue and what I've done to try and troubleshoot it... Create replica in fgdb format via the REST API (createReplica) of a hosted feature service I also exported to fgdb from the Item Details page in AGOL from web browser and got same results Download zipped fgdb and unzip Try to view attribute table in ArcGIS Pro Catalog View in the preview can see how many features there are, but can't see field names or field values Add feature class to a map, can view features in the map Can't view features in attribute table Get an error when trying to access Design->Fields for feature class Export fgdb using the ExportXMLWorkspaceDocument GP tool this completes successfully with any parameters I give it I validate the XML with several validators and it checks out I also did a cursory inspection of the XML and didn't see anything odd If I try to use ImportXMLWorkspaceDocument, I get an 'Invalid XML file' error using python I can do the following read the feature class into a spatially enabled data frame create a list of feature classes using ListFeatureClasses create a list of fields in a feature class using ListFields view all Field properties like name, aliasName, defaultValue, etc. everything looks normal after inspecting the above My only workaround at this point to be able to access this data in a 'working' fgdb in ArcGIS Pro is to use a third party tool (Enterprise Architect) to rebuild the fgdb for me. The steps I take to do this are: Use ExportXMLWorkspaceDocument to export my fgdb to xml Use Enterprise Architect import from XML to create a Enterprise Architect project export from Enterprise Architect project to xml Use ImportXMLWorkspaceDocument to import from the xml from Enterprise Architect to create a new fgdb with same schema as the original one Use Append GP tool to append all features from the original 'bad' fgdb to my recreated 'working' fgdb this works, but it recreates the GlobalIDs for all features when I do the Append this is an issue because there are some relationships that depend on the GlobalID for PK/FK relationships and the preserveGlobalIds environment setting only works for enterprise geodatabases So, it looks like I'm going to submit a support ticket with Esri to see if they can figure out why certain fgdb's experience this behavior. Based on the above, the only odd thing in my feature service are some weird default values (-2209161600000 Update - this shouldn't really be an issue since this is really just 12/30/1899) for date fields that I'm not sure how they got there. These aren't default values for the Editor Tracking date fields, but for other date fields. When I inspect fields via python or ArcCatalog, I don't see these default values. They also don't show up in the XML as default values, it only shows up in the GDB_ServiceItems table in the xs:string for each Record in the fgdb. UPDATE 6/22/2020:  Thanks to Bert Kraan, I pinpointed my issue to the default values for those date fields. For some reason these default values cause issues in ArcGIS Pro and it hasn't been addressed yet in 2.5.0 or 2.5.1. If this happens to someone else, I've got two workarounds. Use ArcCatalog to reset the default values. This is quirky. I had to go to the layer properties->Fields, type NULL into the default value box, hit Apply, go back to the same field and delete the '-2209161600000' that shows up in that box after hitting Apply, then hit Apply again. This needed to be repeated one by one for each date field that had that default value. Use python to iterate through the feature classes in my fgdb, then iterate through fields. If the field had that default value, I used AssignDefaultToField to clear the default and set it to Null. Once I did either of the workarounds, I was able to view the attribute tables in ArcGIS Pro. UPDATE 6/23/2020: Esri support has confirmed for me the existence of BUG-000126591 - "Unable to view the attribute table after exporting the hosted feature service as a file geodatabase consisting of a date field." The bug is currently in the product plan and seems to effect ArcGIS Pro versions 2.4.2 to 2.5.1. Another workaround that support mentioned was exporting to shapefile, but that doesn't work for me due to relationships and long field names. ... View more

Jim, it sounds like yours is a different issue. The main issue we're seeing is when using method=vertex that S123 is not closing the polygon. When using method=sketch and using the free sketch tool, you have to be very careful not to cross over your polygon. S123 only supports simple polygons. In our testing, it was very difficult to create a simple polygon (without crossing over itself) using the freeform tool and the Smart Shape tool didn't really create what we were trying to sketch. ... View more

Jim, we don't have any additional updates. Our support case is still open. Esri has been unable to reproduce the error on their end. In fact, we can only reproduce the error in the affected feature services. If we publish a 'fresh' feature service and try to reproduce the error, we are unable to do so. If a bug gets filed or we get some other resolution, we'll update here. ... View more