sloth4z, may I gently lead you though this, and you can kick yourself afterwards. (Don't feel bad, I do it all the time.)
Imagine you have REAL objects in you hands. You glue some together and take a saw to them. NOW you take another part and glue it over the hole. The hole does not magically appear in that part, because you cut it half an hour ago when only the other bits of the assembly were present.
Remember that SW batabase is a serial solver - a TIME dependent database. That's what is so great about it. Things happen in the order you do them just like the real world. However it does allow time travel (with logical limitations). So if you rolled back to before the assembly cut and then inserted the part, bingo! the hole appears. You can even drag the part back up the tree (think of it as back in time). Now, obviously if it has some dependency on something AFTER the cut, it can't let you do that - there's the logical restriction. Right-click Parent/Child will help find those issues. Using sketches and planes, etc. which were not created in exactly the same order as the features that swallow them can complicate this, but you can usually figure it out.
It is interesting, that those of us who used a lot of older generation CAD systems (note I did say US) often have a problem understanding or at least remembering this all the time. We were so used to just stuffing more entities into a randomly organized database bucket. The line entity that our brain interpreted as the left corner of a "block" (actually 12 independent wire frame lines in space that just happen to touch) could easily be at the other end of a 4MB database from the line representing the right corner. Man, I'm so glad those days are gone..........
Be naughty - save Santa a trip.