Forum Discussion

markmsc's avatar
markmsc
Resolver I
5 months ago
Solved

Working around app navigation inflexibility?

I haven't found that any ways of working around the limited app navigation hierarchy are available, but before totally giving up, I wanted to ask the experts. 

 

I have several Power BI reports grouped into an app.  Some of the reports have several pages, generally when they have shared report-level measures and slicers that can be synced, and are generally different views of the same data.  Other reports may have one page or multiple, but can't be included in that first report file because they use different semantic models.

 

So let's say I have:

 

Report 1: File is called Fruit, and has pages Pear and Apple

Report 2: File is called Root Vegetables, and has one page, Carrot

Report 3: File is called Leafy Vegetables, and has one page, Kale

 

Ideally, I would like app navigation combining all these to result in:

 

Produce (Section)

> Fruit (name of Report 1)

>>> Pear

>>> Apple

> Vegetables (Section)

>>> Carrot

>>> Kale

 

The closest the standard organizational tools let me get is:

 

(Section) Produce

> Fruit (name of Report 1)

>>> Pear (page in Report 1)

>>> Apple (page in Report 1)

> Carrot (page in Report 2)

> Kale (page in Report 3)

 

Or I could dispense with the top-level Produce section and go with:

 

Fruit (name of Report 1)

> Pear (page in Report 1)

> Apple (page in Report 1)

 

Vegetables (section)

> Carrot (Report 2)

> Kale (Report 2)

 

I'm not aware of any creative ways to get what I want.  The reports can't be combined (or separated into singletons) for the reasons I mentioned.  So am I just stuck with that last version, where Fruit and Vegetables have to be entirely separate and can't be grouped together? 

 

Thank you.

 

 

 

  • Hii markmsc 

     

    The best practical workaround is to create a central “navigation hub” report with buttons or links that route users to specific report pages, giving a unified experience. Otherwise, you must rely on flat app navigation with naming conventions (e.g., “Fruit – Apple”), as cross-report grouping, shared slicers, and combined page structures are not supported across different semantic models.

3 Replies

  • Hii markmsc 

     

    The best practical workaround is to create a central “navigation hub” report with buttons or links that route users to specific report pages, giving a unified experience. Otherwise, you must rely on flat app navigation with naming conventions (e.g., “Fruit – Apple”), as cross-report grouping, shared slicers, and combined page structures are not supported across different semantic models.

    • markmsc's avatar
      markmsc
      Resolver I

      Hi, and thank you for this suggestion.  I'm going to mark it as a solution because I agree it will work, though it is not what my users will accept so it's not a solution I can put in.  But I appreciate the suggestion!

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi markmsc ,

    if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

     

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support