I used the Split Tool on our Pavement data to split a segment of road after a construction project was completed to update the pavement condition. It successfully split, then I updated the attributes per segments, and now the segments are gone. But they are still in the Attribute Table (see below). The red circle is where the segments were located. How could this have happened?
I have re-opened the map to see if it was a glitch and they are still missing. It's not the symbology, because I double checked. They are simply missing from the display. Could this be because the two features have the same ObjectID after being split?
Check the 'PCI' attribute value for the features that aren't displaying. I'm assuming a few things here:
You can check the split policy by right-clicking on the layer in the Contents pane > Design > Domains. You can check the default value for a field by right-clicking on the layer in the Contents pane > Design > Fields.
If the above is true, you can do any of the following:
Regarding why this could happen, the Split tool will respect the split policy that is defined on the source geodatabase. This is mentioned in the documentation for the Split tool: Split a feature—ArcGIS Pro | ArcGIS Desktop
Does this help?
Thank you for your response. The PCI was one of the attributes that I updated in the table after the Split and was still within the visible symbology parameters. I double-checked to be sure. No Domains within the data. No default set to the PCI field, and looks like I cannot modify the default. I'm clicking on the area and it's not allowing me to enter any value.
I just got off of a screenshare with ESRI support a couple minutes ago and we made duplicate data, tested in multiple maps, did a Check Geometry on the original data, etc and could not replicate the issue. We did troubleshooting for about 30 minutes or so and ultimately decided it could be a random glitch that occurred since there's no reason it should be happening since my data does not have domains.
Still confused what happened, but fingers crossed that there are no further issues!