Hi all,
I am having some trouble customizing page names due to Visio’s unique-naming constraint. If I want to have multiple “Overview” pages in the same Visio, I have to add some unique modifier to differentiate them. I would like to have some way to hide said unique modifier so that the pages will show up as “Overview” in Cube. Is this possible? Or is there for workaround for this issue?
Example using “rpd” unique modifier:
Thanks!
Hi Alex,
As you might now, we use a // separator in the page name to create page groups. The part before the // is used as the group name and the other part (if present) is used to differentiate between all pages in the group. When there is only one page in a group, we hide the second layer from the UI.
Perhaps we can use this to your advantage. The below example shows you that I can have multiple Overview pages, one for each field. As long as only one page is visible in my group, I will not see the second part of the name.
Example:
In visio
In Cube
It’s currently not possible to have duplicate names inside a page group.
Hi Alex,
It is very strange that you want to have same tabpage names on the same Visual Overview. Because that’s confusing and not user-friendly for the user.
I do suggest that you work with subpages, so tabpages within tabpage “Overview”. When you press the tabpage, it contains different tabpages.
Example:
Configuration: “XX//YY” is the blueprint on the tabpage, where XX is the main tabpage name and YY the subtabpage name.
Hope this helps you further
Hi Matt and Toon,
Toon is correct. This Visio is used in an EPM environment so only certain pages show or are linked to certain EPM entities. That’s the reason why I need to reuse some of the names.
Thank you Matt for your suggestions. I am actually already doing this in some cases (not shown in example).
So the question still remains whether there’s some way to achieve this functionality or do we need to implement a new feature for this?
Hi, I personally believe it is not a valid feature.
Although, you can always create a NF task and assign it to Data Exploration domain and see what their feedback is.
For EPM this becomes a much needed feature since it is the only way to nest pages and achieve a uniform UI.
Note that this is likely in an EPM environment where certain pages are hidden for certain chains, topology selections, etc. In those situations it makes sense to have tab-pages with the same name, with the way it’s currently designed.