Following up on my own comment:
featureLayer.SetDataConnection() will refresh the data connection, refresh the attributes, and refresh the renderer within Pro if already open. If I set the featureLayer's data connection to itself, it refreshes and updates. Here's my template example currently in use, if anybody needs a starting point on this.
My script is doing some QC checks, then outputting the error features into an error feature class within the Pro project's default file geodatabase. I then refresh the default geodatabase before isolating the specific feature layer that's open within Pro to have the data connection reset.
// For each item in the file geodatabase...
foreach (Item gdb in Project.Current.GetGeodatabases().GetItems())
{
// If the project's database path matches the expected default database path...
if (gdb.Path == Project.Current.DefaultGeodatabasePath)
{
// Refreshes the File GDB (it won't auto-refresh within open Pro project)
gdb.Refresh();
}
}
// Create a new map view of the active map in Pro.
MapView mapView = MapView.Active;
// Check if the map view is valid (i.e. a map is open)
if (mapView != null && mapView.Map != null)
{
// For each layer in the map...
foreach (Layer layer in mapView.Map.Layers)
{
// Check if the layer is a feature layer...
if (layer is FeatureLayer featureLayer)
{
// If the feature layer's underlying feature class path matches the error feature class path...
if (System.IO.Path.GetFullPath(featureLayer.GetFeatureClass().GetPath().AbsolutePath) == System.IO.Path.GetFullPath(Project.Current.DefaultGeodatabasePath + "\\" + fc_errors_name))
{
// Refresh the feature layer (attributes and renderer) by resetting the data connection to itself again.
featureLayer.SetDataConnection((CIMStandardDataConnection)featureLayer.GetDataConnection());
//mapView.Redraw(true); // Redraw disabled. It will update the attribute table, but will not update the feature layer's renderer (as of Pro 3.2.2)
}
}
}
}
