I actually spoke to Product Management about this to understand the issue a bit clearer. It turns out, that this is actually due to how holes are handled on the Fusion side. The way that the tapped data is assigned to the hole is different from how INV and SW do the same.
This is something that the Fusion development team is aware of, and I hope to have a solution to it in the near future.
I appreciate you bringing this to our attention, and would strongly encourage all of you reading this to continue submitting cases or forum posts regarding any sort of bugs or missing functionality that you would like to see. One of the primary drivers of new software development is actually you - the users. The more users that want a given enhancement in the software, the easier it is for our development team to justify moving that enhancement to the front of the list. Your feedback goes a really long way in making sure we are putting out excellent products, so keep it up!
Let me know if you have any other questions, or if I can help clarify anything regarding this issue.
Kelbie Ockey
Sr. Implementation Consultant