Latest Contributions by DrewDowling

@SusanTran 👏 👏 👏

Yes, I tried to do this but couldn't get it to work. Esri has said that the widget only supports utility networks. https://community.esri.com/t5/trace-network-questions/can-a-trace-network-feature-service-be-added-to-a/td-p/1350505

I'm getting this error as well. When I try to access the Map Viewer from a VM instance, the map is blank, and the console shows the error. Map Viewer classic draws fine. The VM doesn't have any passthrough GPU, so I'm guessing that's the issue. I get this error in Firefox. I switched to Chrome, and the map viewer loaded.

‎02-14-2024

I like your approach, it's like a hybrid. For what it's worth, we went with the single large catch-all record. My understanding is that if a record has more than 2000 features, it won't calculate or update the geometry of the record during edit operations. We didn't see any performance issues related to this approach.

‎02-12-2024

D'OH

‎02-12-2024

OK, thanks for the info. I don't suppose there is any way to tell how they were initially created?

‎02-12-2024

We have a couple of data stores pointing to the same database with different users. Recently, some user passwords were reset. I'm updating the datastore items' passwords by uploading a new .sde connection file. However, I don't know if the data stores were created with branch or traditional versioned connections in the .sde connection file. My question is, does it matter to a Portal data store item if the underlying .sde connection file was created as a branch or traditional connection?

‎02-05-2024

That's a much better approach, thanks Jason.

‎02-01-2024

Hi Adam I have some code that does something similar that you should be able to adapt. On any feature Insert or update, it queries a table, t.Road_atr, for a related record and updates that record with a value from the feature being updated. //get the road_atr record var results = FeatureSetByName($datastore, 'T.Road_atr', ['GlobalID', 'FNODE', 'TNODE', 'ObjectID'], false) var roadsegid = $feature.roadsegid var atrset = Filter(results, 'roadsegid = @roadsegid'); if(Count(atrset) > 0){ var atr = First(atrset); console(atr.objectID); // atr.GlobalID, return { 'edit': [{ 'className': 'T.Road_atr', 'updates': [{ 'objectID': atr.objectID, 'attributes':{ 'FNODE': $feature.from_interid, 'TNODE': $feature.to_interid } }] }] } }

‎02-01-2024

I'm working on migrating from an ArcMap Parcel Fabric to the newest version. The Migrate Parcel fabric tool works great. All features are migrated, and records are created in the records table. The only issue is that over 20 parcel types are created in the new fabric. Many of these types should be merged together; for example, three different Lot parcel types are created. I want to merge many of these parcel types together. Since records have already been created, I also want to preserve them. I think I can append some parcel types into others and remove them from the fabric, but I'm considering whether this will cause problems. So my question is, can anybody see problems with this approach? For example, If I want to append three parcel types, LotA, LotB, and LotC, the basic steps would be Disable topology Add LotType attribute to LotA Append LotB and LotC into LotA Calc LotType attribute Remove LotB and LotC parcel types from the Fabric Once the Created By Record attribute is appended correctly, then Lots should still be related to the records that created them. If I do an append

‎12-20-2023

Thanks @MarceloMarques . This is an interesting problem. I hope it gets a fix soon, as I can see our editors making large numbers of edits on particularly big projects. For now, my fix was to do the edits in the default version. I'm the geodatabase admin so I have the permissions to edit sde.Default directly. This won't be an option if one of the editors comes across this problem. These are the steps I used to fix the problem should anybody else come across it. From the version that won't reconcile and contains the edits, export the table to a local FGDB Switch to the default version, connected to Portal as a user with rights to edit sde.Default Join local copy of data to feature layer Use the field calculator tool to update feature layer attributes with local copy attributes.

‎12-20-2023

Thanks for the link Scott. The feature service and the editing workflow have been in place and working fine for over a year, so I'm sure it's not the service or how we are reconciling. To test this I created a new version, repeated 20 of the edits and it rec and posted fine. I've started digging into the SQL running on the database but so far can't isolate and COLLATE command using SQL Profiler.

‎12-20-2023

The layer I was trying to edit contained a join. Once I removed the join the error stopped happening and I could edit as normal. I don't recall joins preventing editing before, I wonder if this is a bug?

‎12-20-2023

ArcGIS Enterprise 10.9.1 Pro 3.2 SQL Server 2016 I have branch-versioned data in a feature service. I made approx. 4000 edits in a version. Now however I cannot reconcile this version. When I do, I get a popup in ArcGIS Pro: ERROR: A database error was encountered. Please contact your system administrator to review the server logs. When I check the ArcGIS Server logs, I see this error: Underlying DBMS error [[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Expression type int is invalid for COLLATE clause.] Does anybody know how to troubleshoot this? I'd like to not lose the edits.

‎12-19-2023

Pro 3.2 Branch versioned feature service I get the following error when trying to edit data in a feature service. Could not get the data store associated with this dataset. Please make sure this is a valid and non-virtual dataset The data is from a referenced geodatabase that is branch-versioned. The error might be caused by the .aprx as other editors are able to edit the same feature class in different versions. Has anyone seen this error before?

Online Status	Offline
Date Last Visited	5 hours ago

My Ideas

Latest Contributions by DrewDowling

Re: Publish a standalone to Enterprise (by reference)

Re: Tracing a Trace Network in ExB using the analysis widget

Re: Video card Support for WEBGL2

Re: Editing Existing Parcel Records vs Creating a new Parcel Record

Re: .sde connection file type when registering a datastore Branch or Traditional

Re: .sde connection file type when registering a datastore Branch or Traditional

.sde connection file type when registering a datastore Branch or Traditional

Re: What is the best way to merge parcel types after migration?

Re: Attribute rule to copy attributes from another table

What is the best way to merge parcel types after migration?

Re: Databse error during reconcile reconcile: Expression type int is invalid for COLLATE clause.

Re: Databse error during reconcile reconcile: Expression type int is invalid for COLLATE clause.

Re: Cannot edit version

Databse error during reconcile reconcile: Expression type int is invalid for COLLATE clause.

Cannot edit version

Re: Video card Support for WEBGL2

Re: Editing Existing Parcel Records vs Creating a ...

Re: Attribute rule to copy attributes from another...

Re: Databse error during reconcile reconcile: Expr...

Re: Can Centroid($feature) be used to populate lat...