Latest Contributions by DrewDowling

I didn't do the delete myself but I don't think SQL would have been used. I'll follow up with the analyst who did it. I will say that it is not the only feature class where this has happened. There are 2 others displaying the behavior. All of them are part of a parcel fabric so maybe it is related to that. I will do some more testing to see if I can recreate it. That said, is there a way to fix it? Preferable without having to unversion data. If I delete the validation rule altogether will the related error features get deleted as well? ... View more

Thanks Amir and Dean. I've finally had time to start looking at this again and both you suggestions work for me in theory. The issue is since we are live and have many editors a huge bulk update is slow and will cause many conflicts. @AmirBar-MaorI thought of an alternative approach and would appreciate your feedback. Could I alter the "MUST HAVE RECORD"  attribute rule to only check features that have been created after the initial load date? The create date of all of the original feature is either prior or equal to the day we loaded all our data into the fabric. Only features created after this date are going to genuine violations of this rule.     ... View more

Good luck. I'd like to know what Tech Support suggest. In my case the combination of direct connection and disabling topology speeds up bulk updates by hours. Do you have any attribute rules in place? They can slow things down as well. ... View more

@ArizonaGIS  If you are referring to the original question of doing bulk updates without triggering editor trackling? No I never figured out how to do this with Pro. If you are talking about performance problems then the quickest way to bulk update I found is to make a direct database connection using the SDE user (or whoever is the owner of the Default version) and then use geoprocessing tools.   In pro add the feature class to your map through a direct database connection as the SDE user. Then use geoprecessing tools or field calculator to do an update. Depending on what you are doing you might want to disable topology as well. ... View more

@ChristineLeslie  Ahh that's making more sense. In my head I was conflating the "distance mismatch" data quality layer and the "Adjustment Lines Distance" layer under Analysis. Thank you for clearing it up.       ... View more

@ChristineLeslieThanks for the reply. I'm running the tool on a new subdivision with good survey data. So I would expect the values to be accurate. That said my cogo skills are poor and I can see a particular traverse where the survey distance doesn't match ST_Length by approx 10 feet. Despite this no outlier is created after running the Consistency check or the Weighted adjustment tools. . In this case I should manually enter a distance accuracy of 10ft? So then connecting lines where ST_Length and survey length do match should I enter the smaller mismatch, e.g. .25'? Would it not be better to automatically calculate the distance accuracy value by getting the difference of the survey and ST_Lenght values? ... View more

@Sothea_VOEUNI don't quite understand when you say "The fact is we cannot multiplied the parcel/unit of a condo to represent the lease/ownership when doing a transaction for several times." Can you not create a new Record then use the duplicate parcel tool to copy a condo? How are you condos stored? In our case we store condos in a related table, related to a single "base" tax parcel polygon. In our case duplicating the base polygon won't work since we don't allow overlaps. We are probably going to create a separate parcel type for leased properties. I've been thinking of ways to keep leases in a table and related them to records but don't know how geometry would be created or maintained without an actual Tax Parcel type.   @AmirBar-MaorThanks for your feedback. It's always so helpful.   ... View more

@Sothea_VOEUN @AmirBar-Maor  We are in the very early stages of planning something similar to track leases. Each lease would equate to a new record. We would then add parcels representing lease property. Then when leases expire we would retire the parcel. Might lead to issues when multiple leases at the same parcel. We think there will be stacked or overlapping parcels. ... View more

@Andrew_McClary, @RiccardoKlinger  I never figured out a way to do this with the Pro client. I was able to do it using SQL. The only issue I noticed was that the version difference comparison tool stopped working. This is the tool in the Pro versioning ribbon that lets you see differences between versions. I don't know for sure if the SQL edit broke the tool, it is only a guess. If I created a new feature service with a different name then the version difference tool worked again.   @RiccardoKlingerI get slow performance on a large number of edits as well using feature services. In my case it was the topology. I had better success in bulk updates by disabling topology first and then doing the edit.   ... View more

Yeah I have Pro and have been using that to drop the older ones. Given the number and frequency of these orphan locks I was thinking of scripting a call to the Purge endpoint on the weekends when nobody would be editing, especially not sde.Default. Does that make sense? We have sde.Default protected so the only time it is edited should be during a post operation. ... View more

I too would love to know the answers to your questions. I just discovered we have locks going back 18 months to the database creation and trying to figure out what ones are safe to delete/disconnect. ... View more