Latest Contributions by RussellBrennan

The ActivationExtension pattern only works with geodatabase datasets and feature services. For feature services this pattern is currently limited to feature services published referencing geodatabase datasets and is not working for Hosted feature services in Enterprise and Online ... View more

Hi all,  BUG-000175139 was logged as an issue related to ArcGIS Online feature services and following the AddActivationExtension pattern for custom behavior. This pattern is already supported for feature services published by reference to Enterprise. ENH-000173660 is to support the ActivationExtension pattern with AGOL based feature services, this has not been implemented yet. I would consider reaching out to Support to get your account attached to this enhancement to help prioritize it if you feel this applies to you. ... View more

For heavy analysis happening client side in Pro there is a significant cost to pulling all of the data on the client. We are investing a lot of effort in trying to make this faster from multiple angles. I would push you to look into offline workflows. We recently did some work to better support downloading large datasets: https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/introduction-into-offline-map-areas-prepared-ahead-of-time This might be a good option for your workflows. ... View more

You can only connect to the default version from ArcGIS Pro. Some geoprocessing tools such as Append should work but others may not. I am not sure there is a comprehensive list of which will and will not work. Can you describe some of the tasks. I may be able to provide some pointers to assist with performance. ... View more

@AngelaNesius I sent you a direct message requesting your email. If you have submitted your crash report with your email address I can look it up based on your email address to see if there are additional details to be shared. ... View more

Hi @SimonLux, The optimize append mode on the GP tool will use the server Append operation to perform the append. There are some caveats to using this Append operation that need to be in place, you either need to be an admin on the service (all admins can append) or you need to have enabled the Append capability on the underlying feature service.  When we perform the optimized append we load data into a file geodatabase and upload the data to the server where the server takes over and loads the data directly into the data storage. This is typically a lot faster and has less chance of timing out that our other option which is to use the ApplyEdits operation.  In previous versions of Pro we would do this optimization for you if all the criteria was met for append so I am not sure if your issue is directly related to this new option. In our testing 250k features would never take this long with the optimization enabled, even without it enabled my expectation would be better performance than that. If possible think it would be worthwhile reaching out to Technical Support to get a repro case that we can take a look at. You can view the web traffic using the built in Pro diagnostic monitor HTTP tab in Pro 3.6, this would allow you to identify if the slow append is using Append or ApplyEdits REST requests and could help shed some light on why this is so slow in your case.  ... View more

I think it would be good to review the code. Is the custom tool writing it's own ApplyEdits JSON and sending that via the REST API? I am not sure if this is applicable but have you considered Batch Calculation Rules?https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/calculation-attribute-rules.htm#ESRI_SECTION1_E990820A77724C8AA285A3D23C59E96F ... View more

Hi @jennsmith_ElectricUN  You can uncheck the box to only allow true curve updates by true curve clients. This will allow all clients to edit the geometries of these features, even clients that do not support curve editing. This does come with some risk as it has has potential to densify curves if someone edits these curves with a non-curve aware client. I am a little behind on which clients currently support true curve editing right now. If you are not editing the curves or can implement controls on who has access to edit with this setting you should be safe to do so. I might be able to provide additional suggestions if you could explain exactly what you are doing when you said: "We are trying to use a custom C# script to use the API and trigger the firing of our calculation attribute rules." If you are not editing the geometries in this script I am surprised that the curve checks are causing errors. ... View more

Hi @BrianLeroux , this is currently a limitation in the software. Would you be able to reach out to Technical Support to get an enhancement request logged for this?  ... View more

Hi @RaghavGupta,  When you mention that you are using the add operation, are you doing this via code, from the REST endpoint page? Can you share an example of the payload you are sending? Can you try using the ApplyEdits operation to see if that works? ... View more

Hi @jennsmith_ElectricUN,  The properties for changing the curve options should all be available in 11.3 via Server Manager under Feature Access, you may not be able to change this property if you are not connected as an admin or the user who published the service. These types of modifications are typically reserved for owners/admins. We did add the ability to change this property through the Portal Item page as well but I cannot remember what release that occurred. All versions of Server Manager should have this option.  eg: Since you are working with UN data your service should have the supportsTrueCurve property that @AyanPalit mentions set to true. All UN services should support true curve editing. Additionally all curve options should be supported for all UN versions. There are three options for working with true curves.  Allow geometry updates Allow update of true curves Only allow true curve updates by true curve clients If allow geometry updates is enabled you should be able to set the value to allow update of true curves. If you allow update of true curves you should be able to set the value to only allow true curve updates by true curve clients.  If you set 'Allow update of true curves' to true then anyone can edit true curves, for clients that do not support curve editing this may result in densification of curves when the client writes the edit back to the data source. For this reason it is recommended that you also enable 'Only allow true curve updates by true curve clients'. This allows clients such as Pro, that know how to edit true curves to make edits while blocking edits from other clients that are not yet true curve capable. If densification of curves through editing is not a concern, you do not need to enable this final setting. I think the best doc (I could find) about these curve options is in the offline maps section. While this is about offline maps the behavior is the same. Look in this doc for: "True curves with offline map areas prepared ahead of time"  https://pro.arcgis.com/en/pro-app/latest/help/projects/take-a-map-offline.htm#ESRI_SECTION1_E638E43E632E4C4F969B3D030257CC35  Hope this helps. ... View more