I'm adding users to a newly configured Teamcenter 11.4 environment, and am having a strange issue...when my first user on the system goes to expand a Drawing dataset from his Home folder, Newstuff folder, search results, etc. he cannot. The arrow beside the Drawing Item level does not exist. He can only see the Drawing Revision and any underlying datasets if he opens the Drawing Item in its own tab by double-clicking on it, at which point the Drawing Rev & data is viewable.
I've been working with GTAC and was first troubleshooting this as a Site/User preferences issue, but I've already tried everything they've recommended (preferences_manager to clear User-level preferences, etc.) and nothing has altered the behavior.
I can login to his machine with my user account and the issue goes away; I can log into MY machine with his user account and the issue is present...but I can't for the life of me figure out where the configuration was made that is manifesting in this behavior. I'd rather not add any additional users to Teamcenter until I resolve the problem, to avoid redundant effort to clean up all accounts if this is a persistent problem. Screenshots attached; has anyone encountered this?
Solved! Go to Solution.
It looks like your user doesn't have revisions in the show relations list for your object type.
Note that this may not have been set specifically for the user; it may be set higher up in the organization structure such as Group.
Check what their settings show for your Drawing Item type. Here are mine for Document;
If you can't see Revisions then I'd go to the Organization tab and find out where the <type>_DefaultChildProperties preference has been set.
@jonathan_morris, thanks for the advice; unfortunately this doesn't appear to be my problem. My settings appear to match yours, at least as far as the General-Item-Revisions setting goes.
I checked under Search -> preferences as well, to see if the Site settings listed lined up with what the General->options tab is showing. I believe structure_revisions is the "Real" property name for Revisions...is that what you're seeing in your environment?
I think in your second screenshot you are looking at the setting for a Revision rather than the Item.
If you look in the Item_DefaultChildProperties the value you are looking for is revision_list.
structure_revisions on an Item Revision gives you the associated BOM View Revisions.
It's worth a quick look at the organization tab in options, find the user in their group, then check for settings at each level.
That did it! You're the man @jonathan_morris.
One thing I've noticed over the course of administering site preferences that's a good takeaway for me...I defined a few BMIDE custom objects, based on OOTB Teamcenter Drawing and Part dataset types. It seems like for the most part, the OOTB Preferences associated with the OOTB Drawing and Part Types did not get copied over to my custom Types...I'm going to have to do some pretty tedius/manual preference configuration (or at least much more manual checking and preference reconciliation).
In any case, this solves my immediate issue, many thanks!
Glad to help.
For the deployments I've been involved with we manage the build artefacts in a version control system, including site preferences.
For the preferences we manage the preference_manager xml files which lets us put some of the related preferences together, for example for each object type we have xxx_DefaultChildProperties, xxx_shown_relations, and xxx_PseudoFolder together.
The xml is loaded through preferences_manager when we deploy.
That way it's easy to ensure the changes are consistent, and reproducable between dev, test, pre-prod and prod.
That makes sense @jonathan_morris, I'll give the preference_manager utility a try to copy the preferences I've got set on the item types that I know to be working properly.
Unfortunately we aren't using a version control system outside of the backups manager included in BMIDE, but now that I understand the hassle that mismatched preferences can cause I'll do a better job of maintaining them between my test and prod environments via the preference_manager.