When using BO 4.1.7, if you delete a table from a universe and then export it to the repository, it causes crashes for users when they try to import over the top of the existing universe. This does not happen in 4.1.5 (the deleted tables remain in the universe). Putting the deleted tables back in the universe and re-exporting fixes the problem.
I have verified this bug in our environment - I’m just wondering whether anyone else has noticed this problem. The other solution is to have every user delete their existing universe - not a good option for us. - Scott
When using BO 4.1.7, if you delete a table from a universe and then export it to the repository, it causes crashes for users when they try to import over the top of the existing universe. This does not happen in 4.1.5 (the deleted tables remain in the universe). Putting the deleted tables back in the universe and re-exporting fixes the problem.
Scott, have you reported this bug to BusinessObjects support? We’ve just recently upgraded to 4.1.7, and this could be a real problem in a universe we’re updating now. I’d be interested in knowing whether they plan a patch to correct the problem.