Split tool randomly selects a new polygon

[VanessaSimps]

Hello- I have a strange thing happening when I am editing a polygon using the split tool. 

I select a polygon, then use the split. the split runs, and while it does split the original polygon, it also selects another polygon in another part of the city. I have tried this on multiple polygons in this layer and it always selects the same extra polygon. 

I can work around this by unselecting the unwanted extra polygon from the attributes panel, but I would really like to figure out WHY it's doing this?! 

Thank you in advance, 

Vanessa

[jcarlson]

Really strange... Does the layer have a join on it? Or a spatial index you can recalculate?

[Eugene_Adkins]

To build on @jcarlson‘s idea of a join, what happens if you select (or even split) the unintended/extra polygon? Do other polygons become selected or involved in the split?

[VanessaSimps]

@Eugene_Adkins and @jcarlson - there aren't any joins, but I do have two related tables. I haven't given it a try to select the polygon that keeps selecting itself when the split happens, I can test that out- good idea! Will also try the spatial index re-calc.

So far, when I select any other polygon to spilt, c41 always selects itself and jumps into the party. It's the only one that does this?!

[VanessaSimps]

Attempted to split the party crashing c41 polygon- it splits as expected and no other polygons are randomly selected in the process. 

@Robert_LeClair tested the edit connected as myself (OS) and same thing happens as when I was connected as data owner (SDE).

[Eugene_Adkins]

It would require you to make a copy of your data (due to testing by eventual deletion) into a FGDB, but it would be interesting to see what happens if you were able to replicate the issue in newly exported data.

If the issue is replicated, then you could export that single polygon creating the issue, then delete the original (which would theoretically remove any geometric connection to the other polygons), and then finally copy it back into the newly copied FGDB sourced feature class. It would be a little bit of work but this test may help you determine if there’s some sort geometric tie creating the issue.

Or, if there are no records involved with this specific polygon in the EGDB, export that single polygon, delete the original, and then copy the exported polygon back into its place.

These suggestions would be the next steps in my mind if there are no underlying polygons in your aprx that could cause an unintended selection. If there are other polygon layers (or any features for that matter), I would turn them off and see if the issue continues to happen.

[VanessaSimps]

I was also thinking along this line- delete the offending polygon and redraw it in. 

I don't have any other polygons in my aprx, so I think this is specifically something happening in the feature class that I am trying to perform splits.

[Robert_LeClair]

So it appears you're using an Enterprise geodatabase, correct?  In the internals, there was a similar case where the editor was connecting as the wrong user.  They created a new ArcGIS Pro project, built a new *.sde connection for a GIS Admin and then tried to do the edit.  Worked as expected. 

Question for you - what user are you using to connect to your eGDB?  Do you have the proper read/write credentials?  It also appears you have a RELATE as well.  Another test is remove the relate, try the split operation.  What is the result?

[VanessaSimps]

Correct, this is in an Enterprise gdb. I am connected as "sde", which is the owner of the data.  I can give it a try connected as myself to see if that changes things. 

I have two relates. These two relates are needed in my workflow. I could give it a try without the relates and see if the same issue occurs. I will report back... 

[VanessaSimps · Accepted solution]

Alright- I figured out what was going on!! Thought I should post here incase someone else has a similar issue. I had two relationship classes associated with the polygon that I was splitting. I removed one of these and tested, everything worked fine! I added the other one back in and the error came back.... I also realized that the offending relationship class was configured backwards and I am fairly certain this is why it was causing the random selection of other polygons during the split process.  I actually realized I didn't even need this table related in this phase of the data, so I removed it and am able to keep on moving with the split tool working as expected. hooray!

moral of the story, make sure you have your relationship classes configured correctly!