Hi Chris,
I really like the idea of using federation for this kind of tasks. Some weeks ago I tried a similar calculation concept for dispaying tab content indicators. But somehow the calculation conflicted with regular database operations.
While displaying the federated values worked fine, in my case it was impossible to lock a part. When locking a part, I ran into a timeout error. I assume the combination of 'trigger the calculation' and 'get the item' produced this effect. Or maybe there was a problem with circular references. I just made a quick test of the concept. For the tab indicators the use of real-time calculation was too time consuming.
Regarding this topic, thanks for testing this one! I was able to create a more or less simple method that i can use for onAfterCopy and onAfterVerison events. It turned out, that versioning an item also doesn´t update the BOM counter.
Even copying larger now BOMs works well, so I am happy with the current workaround.
