Latest Contributions by RussellBrennan

@LindsayRaabe_FPCWA I am happy to report that this should be a lot faster in Pro 3.1. We are now grouping edits into fewer round trips to the feature service so it should work a lot faster especially in cases where you are deleting a lot of data. This is for both Delete Rows and Delete Features tools.  We have also made some server side changes that allow us to put more edits into each ApplyEdits request we send to the feature service (Asynchronous ApplyEdits and ApplyEdits with UploadID) . Look for these server side changes in Enterprise 11.1 and the next (summer update) to ArcGIS Online. ... View more

This error maps to one of the following:  FDO_E_DATASET_CANNOT_RENAME  "Cannot rename the dataset with objects already open."  CADASTRAL_E_CONTAINS_COMPRESSEDDATA  "No license available."  WMSCONN_E_MISSING_URL  "URL is missing."  NETWORKLOADER_E_INVALID_FIELD_NAME  "An invalid field name was specified."  E_TEMPMETAFILE  "Cannot create temporary metafile."   Hope this helps. ... View more

Hi David,  As you state the behavior you are describing is expected. The intention of using the source spatial reference in Pro is to avoid adding overhead (aka reprojection) to query requests by default. We report the actual (source) spatial reference of the data which means users are more informed when reprojection is occurring. This is especially informative when multiple layers are published from different spatial references. You are correct that this is a difference in the way Pro handles the spatial reference when compared to ArcMap. Pro will treat feature layers (from feature or map services) as individual datasets rather than as maps. This means that the published map spatial reference is not used by default instead we use the source spatial reference as you describe. Are you able to set the spatial reference of the published map after adding these layers? If you do this, you can set the Pro map's spatial reference to your desired GDA2020 and the transformations you authored should be used. You can do this after adding the data to the map or you can set your Map and Scene properties such that GDA2020 is the default rather than using the 'first operational layer'.  ... View more

Hi Molly, Can you try setting the spatial reference of the map in Pro to a few different options (Web Mercator for example) to see if any other spatial references will allow the the layers display? ... View more

Hi @AndersVolue do you have any code I could use to try to reproduce this error message with my own data? ... View more

Hi @MichaelSnook  Are you looking for geo-database replication or standard database replication? It would be helpful for us to make sure we  are understanding what you are looking for. Would you be able to contact me via PM? I have some more follow up questions about your workflows that I would like to ask you in order to get a better understanding of your constraints. ... View more

Hello, Multi-column unique value renderers are not supported in ArcGIS Online, I suspect that this may be the crux of the problem. If you publish with a single unique value renderer from Pro do you get the expected results? Perhaps an Arcade expression for symbolizing your data may work instead of the multi-column renderer? ... View more

Hi Bart, Can you explain a bit more about what you would like to do with this API. I don't think we have anything at the moment but would like to understand your use case a bit better.   Thanks, Russell ... View more

@LindsayRaabe_FPCWA The Truncate tool operates at the data source level (geodatabase feature class or feature service layer) not at the layer level such as feature layers created in Pro maps or geoprocessing workflows. As such it will delete all rows not just a subset defined by a feature layer. ... View more

Hi @LindsayRaabe_FPCWA  At the next  (Autumn/Winter 2021) release of Pro the Truncate tool will be available to you when working with AGOL hosted services AND you are connected as a portal admin or service owner.  We are also looking to make the improvements you request for deleting features/rows in upcoming releases but this likely will not make it into the software until the release after next (approx. Spring/Summer 2022 at the earliest). As a sort of 'hack/workaround' you can use the button to enable undo on the Delete Rows tool. This should execute very quickly because it is first done on the client (Pro). When you then you click save, this is when we will send edits to the server. Doing it this way will result in fewer edit requests to the server which should speed up the deletion. We have some doc on this delayed editing behavior here: https://pro.arcgis.com/en/pro-app/latest/help/data/services/edit-web-feature-layers.htm but you would sort of have to read between the lines to figure this out on your and how it might benefit in these sorts of situations. Hope this helps. Russell ... View more

Hi MTaft,  In the next release of Pro we will consume a new service property for a 'preferred time zone' that will be available in next releases of ArcGIS Online and Enterprise. This preferred time zone is what Pro will use to display your data, as a service owner/admin you will be able to set this property to whatever time zone you want to use to work with your data. We hope to build on this functionality in subsequent releases. Russell ... View more

If you set up your services such that they are published from a versioned dataset (enterprise geodatabase) and you publish by reference instead of a hosted service, this is already supported.  See: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/offline-maps-and-versioned-data.htm This is also a video from 2.1 (but still relevant) for working with versioned data: https://youtu.be/6VnRHvWWjjA?t=796  With this workflow you can perform reconciles after edits have been synced and choose how you want to define conflicts.  I am not sure if this would be helpful for your needs. Or perhaps your request is more specific to working with Hosted data? ... View more

Hi Ted,  Are you asking for the tool 'Table to Domain' to be supported for hosted services (we currently do not not support this tool with services) or are you asking for something else? Thanks. ... View more

I should also add that hosted feature layers do not currently support storing true curves in the data source. So curves are always 'densified' when created in these layers.  FAQ Article: FAQ: Are curves a supported geometry type for hosted feature layers in ArcGIS Online and the REST API?  ... View more