cancel
Showing results for 
Search instead for 
Did you mean: 

Workset map iView merging error?

Former Member
0 Kudos

I got 2 roles which contains 2 different worksets, their top level and second level navigation tabs are same. I have got workset map iview which is used in both worksets, I also have merge id (same id number) set at second level navigation. It's because of this workset level

Workset-1

---Folder1 (Entry point)

-


OverviewPage

---Folder2 (Merge id and priority set)

-


Overview (Workset map iview, merge id and priority is set here)

-


Folder-X

-


Overview Workset map iview

-


iView

Workset-2

---Folder1 (Entry point)

-


OverviewPage

---Folder2 (Merge id and priority set)

-


Overview (Workset map iview, merge id and priority is set here)

-


Folder-Y

-


Overview Workset map iview

-


iView1

-


iView2

I have 2 different roles, each role has each of the above worksets. When a user gets 2 roles, I wanted to merge above worksets and show 2 folders (folder-x and folder-y) as end result with workset map. But I get below error message when I click on "Overview Workset map iview" or enter at Folder1 level.

Could not find workset location. Check the 'Relative Workset Location' parameter of this iView.

I tried setting "Relative workset location" property but no luck. What changes do I need to make to get this work?

I set iView property "Relative workset location" on Workset-1 as levelsup=2;pathlist={com.xx.workset-1}. I did the same for workset-2.

Am I missing something here?

Can I set the merge Id and priority at iView level?

Thanks

Praveen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Has anyone at all have any information on this topic? We are still unable to merge worksetmap iView, still reporting below error message

Could not find workset location. Check the 'Relative Workset Location' parameter of this iView

Thanks

Praveen

benjamin_houttuin
Active Contributor
0 Kudos

Hi Praveen,

You did nothing wrong, we have the same issue, it seems to be a bug...

We descided to put the WorksetMap iviews (the overview pages) on "invisible" and on "initial object for folder".

This has the advantage that the issue doesn't occure anymore but has a downside that the overview page is not reachable as clickable item in your navigation (only if the user clicks on the folder he/she ends up on the overview page).

This was the solution we implemented and it worked for us... we where thinking of raising a SAP Message for this issue but as this allways takes ages and our issue was fixed we descided not to.

So if the workaround that I discribed doesn't suit your needs then I suggest you raise a SAP Message for this issue.

Good Luck!

Benjamin Houttuin

Former Member
0 Kudos

Thanks for info Benjamin. If we set the WSM iview to invisible in the navigation, it's as good as not using WSM iview in the workset.

I'll keep this thread opened for a while.

Thanks

Praveen

benjamin_houttuin
Active Contributor
0 Kudos

Hi,

You didn't read my post right, besides putting it on invisible you should ALSO set the property "default entrypoint for folder" to true (i called it wrong the first time but this is the right name)...

Tthis results in that the worksetmap IS shown when the user clicks on the folder where the worksetmap is included in.

So it does do more then making it invisible only (what doesn't make any sense)

Benjamin

Former Member
0 Kudos

I'm really sorry Benjamin. Now that you have given me the right property other than property "Invisible in Navigation Areas", I just tried it and looks far better than I initially understood.

I think we can live with your solution and thanks very much for it.

Thanks

Praveen

Answers (0)