Although this might be a value added API; this sounds like more of a training issue. Why would a user granted Product Creator or Library Creator not know what Organization they are in, before creating the Product or Library? My 2 cents...
In our case, we have a brand new installation and we weren't sure what we would need. Now that we've made some projects we see that they don't make sense where they are. So we are already filling up our dB with unnecessary information... Hindsight is always 20/20.
Maybe the admin should be able to move products for a short amount of time or if there are no linked objects in the product? Just a thought.
Why do you have multiple Organizations? Unless you have multiple business units sharing a common Windchill implementation, a single facility should be a single Organization. Using multiple Organizations just adds to the confusion of administrating Windchill.
This was a new installation and my colleague setup multiple organizations. I'm not trying to clean up and can't. I'm beginning to think we should start from scratch again.
We've run into a situation where this would be useful. We went from essentially single org to multi-org. So moving in the first place would have been a help.
We have multiple facets what might be called "business units" and they sometimes change. We also have project ownership issues where a product might change ownership over time. We've also had different interpretations of a "business unit."
There's also the fact that products can't be deleted so it would be nice to move them around. Today we're recreating the products and moving the data to this new org. In general we try not to move them, but things change. If PTC was worried about how products are created within an org they could use some sort of method to create a new product per the new org, move the data, and then mark the old one for deletion and hide it from view.
