Hi everyone,
I'm experiencing an issue with page navigation in DataMiner Cube using the Page shape data field in Visual Overview.
I've created several clickable shapes in Microsoft Visio to navigate directly to specific data pages of an element. Most of them work correctly, but navigation fails for pages containing a forward slash (/) in their names, such as ASI I/O and SDI I/O.
For example, the following Shape Data configuration works correctly, navigating to the "Decoder Services - Overview" page:
Working configuration:

The shape is recognized as clickable, but nothing happens when I click it. The target page exists and can be accessed normally through the element's DATA menu.
Environment:
- DataMiner Server 10.6.11
- DataMiner Cube Client 10.6.x
My questions are:
- Is there a known limitation or issue with the Page shape data field when the target data page name contains a forward slash (
/)? - Is there a supported way to escape special characters or reference the target data page differently, without modifying the connector?
Any guidance would be appreciated.
Thanks in advance!
Hi Daniel,
I've done a quick test on my side and can confirm the behavior you're seeing.
Based on the documented navigation logic, a forward slash is used to reference sub-pages. Since your regular page name already contains a forward slash, this creates an ambiguous navigation path.
I reproduced the problem here, with some additional context:
- Navigation to my page “SDI (In/Out)” shows the same behavior you described.
- Navigation to a regular page works as expected. Navigating to a sub-page also works when using “/” between the main page and sub-page names.

Unfortunately, this edge case isn't supported today, so navigation won't work in this scenario.
(My assumption is that the UI interprets the “/” in “SDI (In/Out)” as a separator, and therefore looks for a sub-page named “Out)” under a main page named “SDI (In”. Neither of those pages exists.)
I'd suggest reaching out to your account manager to report the issue and explore whether renaming the page could be an option. Alternatively, you could consider exposing the most important KPIs or configuration options directly in the visual, potentially removing the need for page navigation altogether.
I realize neither option is an immediate fix, but hopefully this gives you some additional context and practical ways forward.
Kind regards,