Forum Discussion

ghoang's avatar
ghoang
New Contributor II
8 months ago

Open DataExplorer from Dashboard Button

Has the syntax for Navigation Action changed to include workspace name in .v8?

We have buttons that open up cubeviews that have been working fine in the past, but now don't work since we upgraded to .v8.1. 

Others actions like open up workflow or other dashboards work fine. Just DataExplorer that's not working.

TIA

 

 

Cube View
Dashboards
Reports
  • Krishna's avatar
    Krishna
    8 months ago

    ghoang  - Hmm... As far I know the syntax did not change. You can create a support ticket and verify because it was working in V7.4. Please keep me posted on the solution. Thanks

     

     

  • JackLacava's avatar
    JackLacava
    8 months ago

    Yeah, it looks like something is broken. Please open a case with Support to validate it.

    As a temporary (and awkward) workaround, you can use XFPage=CubeViews:MyCubeView . It will open the CV design page, and you can run it from there. I know this might not be viable for users who don't have access to the design page.

    • ghoang's avatar
      ghoang
      New Contributor II
      8 months ago

      It's a default workspace. We have had it for a while in 7.4 and it's been fine, now it's not when we're in 8.1

    • ghoang's avatar
      ghoang
      New Contributor II
      8 months ago

      Also I checked out the post you attached. That post explains opening a "page", the error I have is related to opening DataExplorer / Cubeview.

  • JackLacava's avatar
    JackLacava
    Honored Contributor
    8 months ago

    Yeah, it looks like something is broken. Please open a case with Support to validate it.

    As a temporary (and awkward) workaround, you can use XFPage=CubeViews:MyCubeView . It will open the CV design page, and you can run it from there. I know this might not be viable for users who don't have access to the design page.

    • ghoang's avatar
      ghoang
      New Contributor II
      8 months ago

      Thanks. We'll enter a ticket. The workaround won't work for us unfortunately, because most users don't have access to the design page.