|
POST
|
In our case the residents of the Town are only 'provided' access to the survey form through an embedded iframe on our Town website, so I'm not sure if there is really any visible mechanism for them to open the survey in the Survey123 app unless they somehow yoinked the url for the survey from the HTML source or browser devtools. We don't provide any link "to open this in a separate page" or anything like that. So I feel like this is not likely our issue, but I can't guarantee it.
... View more
07-15-2025
06:30 AM
|
0
|
0
|
1293
|
|
POST
|
I don’t think any of that is relevant to me unfortunately — the webhooks are firing successfully about 50 times each day, when a new form is submitted. It seems that one or two simply don’t fire off the webook for some reason. To follow up in you’re first sentence actually: if a user uses Survey123 app, the client sends the webhook, rather than AGOL? If using a browser, is the browser client also sending the webhook payload? I assumed this would be coming from AGOL and not the clients. Actually it must— the json includes the objectid which isn’t created until the submission hits the AGOL server and registers a new record in the hosted feature layer?
... View more
07-14-2025
06:55 PM
|
0
|
2
|
1311
|
|
POST
|
I have a handful of Survey123 forms (AGOL hosted) that have webhooks registered to deliver a payload for a Power Automate cloud flow trigger. 95% or more of the time everything works fine. But I'm noticing this week that there are many that simply don't fire the webhook payload to Power Automate. For example, a form submitted at 1:32PM triggered correctly a form submitted at 1:36PM - no record of any trigger a form submitted at 1:37PM triggered correctly There have been 6-7 of these instances in the past couple days. I hate that I have to baby this thing and make sure stuff is coming through. The Survey123 forms are for our Town residents to request services; I process them in Power Automate to ingest them into our Town's work order management system, and the customer gets a confirmation email, etc. Is anyone else experiencing something similar now or in the past? I started a ticket with ESRI just now but wanted to reach out to the community as well. Thanks in advance! P.S. I actually have two identical webhook payloads for each form, one goes to our Testing environment flow (which doesn't follow through on processing requests), one to our Production environment flow. Neither one triggers in these instances.
... View more
07-14-2025
11:26 AM
|
1
|
6
|
1356
|
|
POST
|
lyr = FeatureLayer(url=layer_url, gis=gis) # establish a FeatureLayer object from AGOL source attachment_manager = lyr.attachments attachment_list = attachment_manager.get_list(objectid) # this is a list, and each item in the list is a small dict of attachment attributes if attachment_list: # ignores a blank (empty) list for attachment in attachment_list: # download attachment attachment_path = attachment_manager.download(objectid, attachment["id"]) # this returns a list but it is a single string (path) I've tried to boil down my code I'm using to the above. I am experiencing an issue where, for example, a Survey123 form submission (saves to an AGOL hosted feature layer) has 4 attachments and it is taking > 15 minutes to download all of the photos. Each photo is about 9mb. Each one takes > 3 minutes to download. This seems extremely slow. I haven't tried @sakurai workaround but I just wanted to put in my experience about the slow download behavior.
... View more
03-06-2025
06:53 AM
|
1
|
1
|
2158
|
|
DOC
|
@JordanCarmona I still agree and I'll stay it again since ESRI still hasn't provided a satisfactory response on this issue. The best I got was a suggestion to write custom command line scripts to parse the update tool's -c text output. The -i flag is for installing and is an optional argument as the referenced documentation mentions. If you only intend to check for available patches you would not specify that flag. The -c flag is for running the tool in console mode to write output to the terminal. You would need to parse the output with a Batch or PowerShell script then subsequently send an email based on the logic you desire. The other flag of note is -o and has a default value of 'never', meaning it would never delete installed patches after they were downloaded and applied to the machine. You could also provide 'always' to clean up afterwards and conserve disk space. I feel like the need to write custom code to parse the unstructured text response from the command line tool for each Enterprise machine is a needlessly complicated burden that ESRI is putting on the user to create and maintain, when just signing up for email notifications seems like such an obvious and normal solution to reach end users for security (and other) patches. This is surely not reinventing the wheel. ESRI previously had email blasts going out based on check-boxes about what ESRI components you are interest in, in order to receive updates via email (https://go.esri.com/emailPreference[...]). I don't think this URL works anymore. That may have been a recent change. Here's what it used to look like last year. If users writing custom code is the only sure-fire solution that ESRI can offer (the mobile app is definitely not a proper solution), then we might as well write code that directly checks the whole structured .json for changes for all of our desired components at once. Why doesn't ESRI just write a simple tool that does that and provide it to everyone? Are these decisions just geared to forcefully funnel people to the app, despite all of its known limitations?
... View more
01-23-2025
05:43 AM
|
0
|
0
|
18150
|
|
POST
|
Wow I think that was our problem. I moved a stream service from my Portal root to a subfolder for organization purposes. I didn't putt 2 and 2 together to realize that was the only change I had recently made, and that this had suddenly borked our stream. We were about to start completely tearing down and rebuilding all of our services to try to figure out the problem. You definitely saved us a lot of headache. Did anyone from ESRI ever respond about this issue? I wonder if this is a bug that continues beyond 11.1?
... View more
01-21-2025
09:36 AM
|
0
|
0
|
1583
|
|
IDEA
|
I would like to be able to unlock my users as well. Can this just be added to the (...) menu for each Member?
... View more
12-03-2024
01:05 PM
|
0
|
0
|
2323
|
|
IDEA
|
@SSWoodward can you please show the Export Features options for removing attribute rules? This does not seem to exist on my end. ArcGIS Pro 3.1. These options or environments are also NOT shown on the documentation page for Export Features tool.
... View more
09-10-2024
06:32 AM
|
0
|
0
|
2343
|
|
POST
|
I have a lot of feature classes that automatically calculate an ID upon an 'insert' operation. This uses a MS SQL Server database sequence, which was also set up through ArcGIS Pro. This attribute works as intended for my purposes. However, today I noticed that when I use Export Features to copy ANY (1 or more) of these features to a new feature class location, such as a file geodatabase, the attribute rule of the copied layer runs on the FIRST feature only, as if it was performing an 'insert' operation, but does not perform the rule on any other feature. First of all, this is undesired behavior for any of the features to have their ID's recalculated when using Export Features. But second, why is this operation only happening on the first feature and not all of them? Is this bug? Or if this behavior makes sense, can anyone explain? I am using ArcGIS Pro 3.1, and this also occurs when using ExportFeatures with arcpy outside of Pro. P.S. There seems to be no method of copying a feature class and having it drop attribute rules. Even though there is a thread in the ESRI forums that says this is an option in Export Features tool, I do not see any relevant option for it. P.P.S This also happens on copies of copies of copies of the data, each of which inherits the attribute rule. It's not just when being copied from the SDE source. It also happens when the source is in a File Geodatabase as well. I will try to do some tests with another attribute rule that doesn't rely on a database sequence to see if it performs an 'insert' operation on the first feature no matter what the specific Attribute Rule content is.
... View more
09-10-2024
06:23 AM
|
0
|
0
|
665
|
|
POST
|
@LISARAYBURGodot Which fix worked for you? A few different things have been suggested so I am curious. Also, are you using Dedicated, or Shared resource pooling?
... View more
09-01-2024
09:14 AM
|
0
|
1
|
3424
|
|
POST
|
I’m glad to hear these experiences. One of my coworkers has 3.2 Pro while the rest of us have 3.1 and the constant warnings about compatibility were not expected. We are definitely going to avoid any version mismatching in the future and will be enforcing 3.3 Pro across the board when we upgrade to 11.3. I also have the SQL Server 2016 incompatibility issue with 11.3 but in my case I am going to migrate our SDE’s to Postgres instead of waiting on SQL Server upgrades (expected in 2 years 😔).
... View more
08-29-2024
12:16 PM
|
1
|
0
|
4084
|
|
IDEA
|
I'd like to pile on another request for absolute paths as a manual option for project data sources. My example is that I use network UNC paths for a shared network drive where we store a lot of GIS data and ArcGIS Pro project files. There are different windows file shares being served from that networked server for different reasons (e.g. one source is read-only for most users so they can't modify core data). I have use cases for using UNC paths sometimes, and mapped drives other times. I have a project: \\networkedMachine\sharedFolder\ProjectFolder\Project.aprx The project points to some data: \\networkedMachine\OtherSharedFolder\Data.gdb If I open the .aprx from the network UNC path above, it's fine. But some users have \\networkedMachine\sharedFolder\ mapped as a drive (let's say G:\ drive) in Windows. If someone were to open the .aprx from the G:\ drive like so: G:\ProjectFolder\Project.aprx The project will open, but the all the data paths are broken because ArcGIS Pro is trying to point data to G:\OtherSharedFolder\Data.gdb. This needs to retain the original UNC path (different file share path) as it was originally set in the project. If I'm not mistaken, Pro is basically was considering \\networkedMachine\ as a relative root folder of the project, and it is modifying paths relatively across the board within the project based on the root folder of the project .aprx being different when being opened from the mapped drive. I'll also drop a line at the end here that ArcGIS Pro project file/content pathing behavior is unnecessarily opaque and simultaneously convoluted and hard to understand among the options of using "Save As", creating a new project from a Template, or copying an .aprx out of its home project folder alone and opening in a new folder. Specifically in regards to how Pro retains (or not) paths to original project default.gdb, default toolbox, if it creates a sub-folder for the project, etc. I don't see why we can have more explicit wizard-like options to control how we want ArcGIS Pro to treat project components when they are being copied, spawned from a template, etc. It's a big pain point trying to get my users migrated into Pro when our 'best practices' for ArcGIS Pro project data management sound like we're navigating a minefield just to spool out projects (and their associated data) in a deliberate, organized fashion.
... View more
07-31-2024
02:09 PM
|
0
|
0
|
3711
|
|
DOC
|
I'd like to offer my unsolicited opinion that the ESRI Support app looks clean but in reality the functionality is absolutely trash... from my perspective. I'm feelin' spicy about it... I have no options for what notification types to get. I get 5 to 15 notifications a day and very rarely is it relevant to me. I have no options for search or filter. Most importantly, the patch tab is only showing a handful of recently release patches, most of which have no relevance to me or my Enterprise build, and it's not even showing that there was a security patch from a few months ago (which I missed until this week because... guess what... you all have effectively have no security patch notification system). I hope I am wrong and embarrassed by someone correcting me, but this feels like you all are ignoring very serious concerns about getting security updates as fast as possible in this day and age. Please do not suggest that we automatically patch servers with no monitoring. However, if you can explain the command line tools available with patchnotification to 'flag' that an update is available so that I can write myself a little script to send myself an email -- without automatically installing a patch -- that would be useful.
... View more
07-16-2024
03:14 PM
|
0
|
0
|
20399
|
|
POST
|
Update: I got a response from an ESRI engineer: Microsoft’s mainstream support of SQL Server 2016 ended in July 2021, and extended support ends in July 2026. Because Enterprise 11.3 is supported well beyond that date, we could not offer support for SQL Server 2016 with ArcGIS Enterprise 11.3. And a separate response from an ESRI support rep: Please refer to the screenshot that I got from this link as attached below:- Just to let you know, the 'older ArcGIS clients' referred to in the picture are pointing to all old versions of software configured with ArcGIS Enterprise. This includes the SQL Server version as well and is not limited to the DBMS version. As stated in the picture, you still can perform a normal task within the ArcGIS Enterprise and Pro, and as stated in my previous email, the connectivity between your Pro and ArcGIS Enterprise to the SQL Server will not be affected. However, if you open any datasets that need a compatible version of the SQL Server, then only you will observe an error message as stated in the screenshot. Aside from that, I don't think it will give an issue to your deployment.
... View more
06-19-2024
06:17 AM
|
2
|
4
|
4429
|
|
POST
|
I've had the issue of domains not being correctly updated/reflected in web maps when republishing after changes were made to a domain. The 'fix' if you can call it that on my end seems to be some combination of closing all other instances of ArcGIS Pro except for the project I'm publishing from; close all but the map in question within that project being used for publishing; recheck domain settings/values save & close the project and restart it to make sure it's loaded fresh; republish again maybe do this twice? It's pretty wonky sometimes. I'm not sure why it takes sometimes and not others. Enterprise 11.1, SQL Server 2016 for SDE, ArcGIS Pro 3.1
... View more
06-19-2024
05:22 AM
|
0
|
0
|
3698
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 9 | 3 weeks ago | |
| 1 | 03-28-2026 08:15 PM | |
| 1 | 03-08-2026 12:16 PM | |
| 3 | 07-22-2025 07:31 AM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|