I'm creating a node network, selecting faces in groups and blasting/deleting them, then adding and repeating this.

However, changing any of the selected faces at one of the top group nodes, results in changing primitive numbers which causes a cascading effect: any downstream nodes will now be blasting different primitive IDs.

I have to traverse down through the entire network from where I changed the group nodes to reselect faces.

Can anyone suggest a better workflow? A knowledgeable colleague mentioned I can group by assigning and grouping by attributes rather than primitive IDs from the get-go, but may be subject to errors when geometry starts changing.

You can create an additional attribute to store the original primitive/point ID, for instance “pid” on primitive.
Then use this “pid” attribute to blaste/delete any primitive you want.

akirasun_sh
You can create an additional attribute to store the original primitive/point ID, for instance “pid” on primitive.
Then use this “pid” attribute to blaste/delete any primitive you want.

That was the suggestion he offered as well. Thank you!