Latest Contributions by MollyMoore

‎06-15-2021

I'm looking to set up a Dashboard for data QC that allows users to fill in one or two fields. As I understand, there are a few workarounds for editing data within Dashboards. 1.) Including a Survey 123 form as embedded content - I have not been able to get this to work because the database that I am working from has already been created and I have been unable to create a Survey 123 form from it due to it not being set up to enable the supportsApplyEditsWithGlobalIds option. This does not seem like an option. 2.) Creating a web application that includes an edit widget and use it as an embedded content - I have done this, but I can't find a way for the embedded web app to support zoom or filter actions, so it kind of defeats the purpose. Is there a way to set up a zoom or filter for embedded web apps within the Dashboard? 3.) Is there another workaround to set up editing of data within a Dashboard?

‎02-08-2021

This did the trick (with the single quotes). Thank you all!

‎02-08-2021

Thank you! This works for the given example. However, I'm unable to pass a list query. I can pass the list query without error, but it ignores it and loads all features into the feature set. This is what I'm passing: nha_expression = "NHA_JOIN_ID IN ({0})".format(','.join(nha_ids)) nha_core_fs = arcpy.FeatureSet() nha_core_fs.load(nha_core_url,nha_expression) The nha_expression looks like this: 'NHA_JOIN_ID IN (xxx42966,xxx42967,xxx43009)' I am able to drop the necessary records after I load in the features with an update cursor, but I figured it would be a lot more elegant and faster to just not load them in the first place through the where clause, so if anyone has ideas about why it's not honoring the query, I'd appreciate it!

‎02-05-2021

Yes, this is being used in a toolbox that I'm running through Pro. Do you mean that I need to bring in the data and then query it in another step? Or is there a way to separate the query from the URL in the feature service request? If the latter, is there an example of this somewhere? I couldn't find anything like this.

‎02-05-2021

I have not. I figured since it was letting me use the feature service layer without the query that this wasn't the issue. But, I'll try this now.

‎02-05-2021

I am pretty new to working with the REST API and I'm trying to query a feature service on our organization's server using arcpy. Here is my code: fs_url = r"https://maps.waterlandlife.org/arcgis/rest/services/PNHP/NHAEdit/FeatureServer/1/query?where=STATUS='C'&outFields=*&returnGeometry=true&f=JSON" fs = arcpy.FeatureSet() fs.load(fs_url) I have tried to change the options for nearly all of the parameters here and tried including other parameters or excluding some of these. I keep getting the following error: RuntimeError: RecordSetObject: Cannot open table for Load I'm able to load the feature set fine without the query and have looked at a ton of resources online and can't find any solutions that have worked. Can anyone help me out with what I'm doing wrong? Thanks!

‎10-16-2020

I have a feature service set up that includes several relationship classes between feature classes. When I select features by attributes in the origin layer, I then click 'select related records' for the desired layer. The attribute table of the desired table opens, but no records are selected. When I manually select records, the selections seem to work better. There are 1,785 records selected in the origin table when I run the selection query. Are there any kind of limits or stipulations when using relationship classes with feature services? Any ideas about what I can do to fix this? This is happening in both ArcGIS Pro and ArcMap 10.7.

‎07-17-2020

I've been generally frustrated with Pro's lack of ability to complete simple tasks without being so slow that it is unusable. Most frustrating right now, is the speed that it takes for Pro to update after setting a definition query on a layer. Is there some reason why this is so slow or something I can do to make it faster? Currently, if I set a definition query, it will take around 30 seconds to a couple minutes for the window to become active again.

‎05-08-2020

Ahhh, I'm connecting to Access 32 bit. This is probably the issue, right? Is there a workaround for this at all other than the 64 bit install of Access?

‎05-08-2020

I have a Python script that connects to an Access database, brings in some data, and then appends to a feature layer in ArcGIS. This script runs okay as a stand-alone script, but I am having issues creating the connection to the Access DB from within ArcGIS Pro. I installed the PYODBC module in the Python manager. Then, when I try to make a connection to the Access DB with the same code that works in the stand-alone script, I get this error message: pyodbc.InterfaceError: ('IM002', '[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified (0) (SQLDriverConnect)')‍ This happens whether being run in a tool or whether the following code snippet is run from within the Python window in Pro: conn = pyodbc.connect('Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=P:\\Conservation Programs\\Natural Heritage Program\\Data Management\\ACCESS databases\\POND_entry\\POND_be.accdb;')‍ Any insight would be much appreciated.

‎04-13-2020

I am also running into major speed issues in ArcGIS Pro 2.5 when trying to accomplish very simple tasks that makes Pro practically unusable for my workflows. Right now, my biggest issue has been with definition queries. When I set a definition query on a feature service layer with around ~11,000 features, it takes anywhere from 3-8 minutes for the Pro project to become responsive again. When I set a definition query on the same dataset with the same computer and connections, it updates instantaneously.

‎04-10-2020

Anyone else notice that ArcGIS Pro is super slow to update after establishing a definition query on a feature service layer? I will list a new definition query on a layer with ~11,000 records and press okay and then it will take about 5 minutes before I am able to open attribute tables or do anything in Pro. In ArcMap, it is almost instantaneous with the same feature service layer.

‎02-18-2020

I'm continuing to have issues with previous functionality not working after the update to Pro 2.5. I'm trying to use arcpy.da.InsertCursor() to insert features into a feature service feature layer. This is something that I did fairly frequently without problems prior to the update. After the update to Pro 2.5, I am getting the following error: RuntimeError: ERROR: code:500, Unable to complete operation., Unable to perform applyEdits operation., An error occurred., Internal server error. I am attempting to insert into a feature service layer that is in a project in ArcGIS Pro. I'm able to edit, create, delete fine in the feature service manually. An example of the code I'm trying to run is below: values = [refcode,geom] fields = ["refcode","SHAPE@"] with arcpy.da.InsertCursor(elem_poly,fields) as cursor: cursor.insertRow(values)‍‍‍‍‍‍‍‍‍‍‍‍ Any ideas about what I should be doing differently?

‎02-17-2020

Okay, after much trial and error, it seems that a period was the culprit. A period used to designate version number of the tool in the alias and label were breaking the tool after the update to Pro 2.5.

‎02-17-2020

I'm trying to run the custom python toolbox from within Pro. I'm struggling to understand why I need to import the toolbox into the toolbox itself - and thus struggling with how I should try to write this in within the script. I did create a new toolbox in Pro and copy and pasted my custom toolbox into it and that worked. However, I'd like for the tool to be able to run from a static file location without having to copy/paste into a new toolbox because others will be using it within our organization and it's easier to push out edits like this.

Online Status	Offline
Date Last Visited	‎02-23-2026 12:05 PM

My Ideas

Latest Contributions by MollyMoore

Edit data within an Operations Dashboard

Re: Error when querying REST API

Re: Error when querying REST API

Re: Error when querying REST API

Re: Error when querying REST API

Error when querying REST API

Select Related Records not Working Properly

Definition Queries in Pro are very slow to update

Re: PYODBC connection to Access not working within ArcGIS

PYODBC connection to Access not working within ArcGIS

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

ArcGIS Pro Very Slow to Update Definition Query

Arcpy InsertCursor not working for feature service with update to ArcGIS Pro 2.5

Re: Error 000819: The tool is not available or is unassigned with update to Pro 2.5

Re: Error 000819: The tool is not available or is unassigned with update to Pro 2.5

Accessing feature layer attachments with R-ArcGIS ...

Issues with using Python to update field visibilit...

Print widget error - fails to print

Re: Print widget error - fails to print

Editing/Viewing Related Records for Non-Hosted Fea...