I recently encountered this bug when importing a mxd in Pro.
BUG-000146074
Synopsis: Importing a map document from ArcMap 10.8.1 into ArcGIS Pro 2.9 and 2.9.1 results in layers with feature exclusions.
Description:
Importing a map document in Pro results in layers with feature exclusion sets that did not exist in the original map document. These are layers that are typically created by selecting features and choosing Make Layer from Selected Features from the layer right-click menu.
Steps to reproduce:
Solved! Go to Solution.
I see BUG-000146074 in the "internals" and its status is "In Review" - I suspect the ArcGIS Pro Dev Team is examining it - hopefully resolved in a future update.
I see BUG-000146074 in the "internals" and its status is "In Review" - I suspect the ArcGIS Pro Dev Team is examining it - hopefully resolved in a future update.
Grr, I've just finished manually converting about 150 mxds to Pro and have republished them using Pro. Any idea if this will affect the data in the map services as the underlying data changes (it's my understanding that selection sets break down as the data changes). And if I go back through all the Pro projects and remove the feature exclusion sets, do I need to republish the services? That would be a REAL pain...
Chris
also wondering if there's a way to programmatically clear the feature exclusion set using python?
Can you create Exclusion Sets directly in Pro?
Or are Exclusion Sets an artifact of having a layer selection applied in an mxd that is imported into Pro?
I have the same problem when importing mxd created with ArcMap 10.6.1 in ArcGIS Pro 2.9.14
I reviewed BUG-000146074's update and this is not reproducible in ArcGIS Pro 3.x releases now. It was an issue with ArcGIS Pro 2.8, 2.9 and 2.9.1.
Thanks for the reply! I just want to mention that Pro 2.9.14 was released 2 weeks ago (21 novembre 2024) and the bug is still there.
That is correct - ArcGIS Pro 2.9.x has this BUG but when you upgrade to ArcGIS Pro 3.x (current version is 3.4) then the bug is no longer present.
@BrianRobeson, @Robert_LeClair, @ChrisDunlop or @ColForbin do you know if this bug has any effect (i.e. does it exclude some features)? If so is there are a Python method to help automate the fix? We are also re-publishing a large number of services and hoping not to have to manually fix each layer, and we are stuck on Pro 2.9 for a while. In all layers I've checked the feature count stays the same after removing the feature exclusion set.