I’ve had this issue persistently when migrating from 3.x to 4.x. Like you, I had to create a class and hide the class. Once in 4.x alone, it seems to be OK.
But I’m finding other migration bugs too. List of values for example. An LOV from 3.x won’t regenerate in 4.x - even if the users tries to refresh it. I’m having to manually regenerate all my LOVs in 4.x.
I don’t think the migration wizard it’s all it’s cracked up to me when migrating between versions!
But we are on 3.1 and are not migrating, just having an issue in general with this when creating reports, that I can’t get WebI to hide my classes and objects.
I would imagine that these have been hidden when using other service packs.
You are sure that your client is at the same patch level as the server?
In addition, am I remembering correctly that you have had minor universe corruption issues before?
This is the same universe that has caused head ache before, but I seem to have found a fix for those problems.
This problem with hidden/shown objects are the same with us and our clients that use the universes (on misc. SPs). It’s only a problem in this one universe, and not in others we have where the hide has been done in the same SP (parallell development).
It’s not a huge problem as the objects we are hiding are mostly for use for supporting other objects, calling procedures and such, but it’s confusing for clients with these classes (and some individual objects in shown classes) that they don’t have any use for.
Thank you for that helpful link, Mark. Unfortunately not mentioned for SP7 As it is only a problem in one of our universes, and only for WebI and not DeskI, maybe nobody else has come across it either.
My experience is that hidden Objects are very flakey in v3.1
If you have a Class of hidden Objects they remain hidden when creating a report from scratch. However, if you open the query panel in a report that uses previously visible Objects (now hidden), they remain visible and available to use in new queries.
We’ve tried splitting it up, but the clients would have to combine so many universes for most reports, as it’s a complicated business area where most reports span over several “sub-areas”. And other than the product not being able to cope with the universe size, it would probably mean more maintenance having 22 universes with 500 objects in each