Merging roles into 2nd Level Nav directly

[Former Member]

Hi All,

Firstly, I have read posts similar to this on the forum however the workarounds provided are not suffucient.

What I need to do is have a "base" portal role that defines the 1st level navigation, as well as some second level. I then want other roles (for specific tasks) merging in at the second level directly. I do not want them replicate the first level navigation structure defined in the "base" role. There are several reasons to do this, to simplify design, reduce maintenance, included replicated config for multiple languages.

Example: Base role

: Home [entry point] [folder]

- My Role {merge ID aaa} [folder]

- Reports

- Communities

- Corporate Information

Example specific role:

{no entry point}

- My Role (mergeID aaa) [folder for config, referred to below]

- Manager Self Service

When I config the folder "My Role" I do not set it as an entry point to avoid displaying in 1st LN. To link into the second level nav I create a merge between the two folders (one in the base role and one the specialty role - shown above). The problem is then the folder "Manager Self Service" does not appear in the detailed navigation.

Is what I am trying to do possible? Has anyone had success?

Edited by: Justin Hume on May 22, 2008 9:22 AM

Edited by: Justin Hume on May 22, 2008 9:24 AM

Edited by: Justin Hume on May 22, 2008 9:26 AM

Edited by: Justin Hume on May 22, 2008 9:27 AM

[Former Member · Accepted solution]

Hi Justin,

Below is the sample setup which we use for our portal with merge ID. Note that I only use merge ID on the top level navigation with the name of the role identical but with a different ID.

MyWork (Role set with Entry Point and MergeID "MyWork". Role ID is MyWork_Coll)

Collaboration Room (Workset)

Room Directory (Page)

MyWork (Role set with Entry Point with MergeID "MyWork".Role ID is MyWork_MSS)

MyTeam (Workset)

Performance Management (Page)

The result we got (if a user has been assigned with the 2 above roles) was that on top level navigation, all user see only one tab (MyWork). On the second level navigation, they will see Collaboration Room and MyTeam.

Hope that can assist in your design for mergeID. I hear that its possible to merge at a lower level but I did not try that as the above concept works perfect for me at this moment.

Hope that helps.

Ray

[Former Member · Accepted solution]

Thanks Praveen & Ray,

Praveen: unfortunately setting the entry point to yes on folder "My Role" (mergid aaa) in the second role places it into the first level navigation.

Raymond: I am currently doing what you have suggested. The problem is I have near 70 roles in a multi language configuration... this means there are similar merge IDs for 150 PCD objects when including second and third level naivgation. As you may imagine maintenance of these merge IDs is a problem - especially with multiple content administrators and multiple languages! (The language problem is a separate issue but would be resolved by merging directly into lower levels).

I'm hoping to hear how to merge directly into a lower level without merging at the first level. Whenever I set the merge id on the second role without an entry point, it is not visible. When I make that folder an entry point it inserts into the first level, despite having a merge id equal to that in lower level in another role.

[Former Member · Accepted solution]

To close out this thread it is not possible to do what I wanted do, as of Service Pack 15.