Thanks for the help Jack!
I tried this now, and apparently the parent filter expects the E#, not the P# just as a note. But regardless it's still giving me an error. "The item was not found. Entity, Parent, -1"
Can you expand a bit on your idea with the custom calculate? For this consolidation member it looks to me like it still requires the parent and when triggered as a DM job, i still have the same interface for filling out the entity-parent relation that i cant figure out how to input.
I guess I can trigger the custom calculate through the component selection changed interface on a component, or with brapi.Finance.Calculate.ExecuteCustomCalculateBusinessRule, but I wouldn't expect these either to process the member filters passed and I want this processed in parallel not looped.
As I said, blindly going for .Parents will likely result in invalid combinations, which is where you get that error.
As for Custom Calcs: once you drop in code, you can build the combinations yourself and execute them with BRApi.Utilities.StartDataMgmtSequence. There are a few other parallelization techniques, like creating low-level .Net threads.
All of this sounds really overkill just to get a refresh though. I would simply consolidate all immediate parent entities, or break down the interface to work with subsets of the Entity tree and target just the top of that.
