cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

breadcrumb is not working as expected - missing query parameter

 

Hi,

 

I am trying to implement breadcrumbs in the powerapps portal, I add the following breadcrumb snippets into Layout 1 column web template.

 

 <ul class=breadcrumb>

    {% for crumb in page.breadcrumbs -%}

      <li> <a href={{ crumb.url }}>{{ crumb.title }}</a> </li>

   {% endfor -%}

   <li class=active>{{ page.title }}</li>

</ul>

 

It shows the breadcrumbs correctly when I navigate to a different page, however when I try to navigate back to the parent page by clicking the breadcrumb, it doesn't go back to the parent page successfully. The reason was because the <a> tag constructed was missing the query parameter which identify the id. 

/en-US/account-maintenance-form/?id=xxx

 

Is there any way to add the query param onto the breadcrumb.url?

 

Thanks,

Harry

harryc2020_0-1600152116150.png

 

10 REPLIES 10
OliverRodrigues
Most Valuable Professional
Most Valuable Professional

Hi, there is already an existing code for the breadcumbs logic

 

For example my Layout 1 Column code is like this:

<div class="wrapper-body">
    <div class="container">
        <div class="page-heading">
            {% block breadcrumbs %}
            {% include 'Breadcrumbs' %}
            {% endblock %}
            {% block title %}
            {% include 'Page Header' %}
            {% endblock %}
        </div>
    </div>
    {% block main %}
    {% include 'Page Copy' %}
    {% endblock %}
    <div class="push"></div>
</div>

and finally I have another Web Template just for breadcumbs:

{% assign title = title | default: page.title %}

<ul class="breadcrumb">
 {% for crumb in page.breadcrumbs -%}
 <li>
  <a href="{{ crumb.url | h }}" title="{{ crumb.title | h }}">{{ crumb.title | truncate: 24 | h }}</a>
 </li>
 {% endfor -%}
 <li class="active">{% block activebreadcrumb %}{{ title | h }}{% endblock %}</li>
</ul>

 

hope this helps
------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.




If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Power Pages Super User | MVP


Oliver Rodrigues


 

Hi @harryc2020,

This is because the template is attempting to be generic - if my Parent page is for Opportunity, and my Child Page is for "Products," then they likely have two different "id" params. If both parent and child page reference the same record, you'll have no problem.

You'll want to make the below changes, keeping in mind that this can cause odd behavior if you setup your hierarchy like the example I used - in which case you'll want to make this a unique Web & Page Template combo. Every page back to Home will continue the ID, until you've clicked a link that replaces it.

 

<ul class="breadcrumb">
 {% for crumb in page.breadcrumbs -%}
 <li>
  <a href="{{ crumb.url | add_query: 'id', params.id }}" title="{{ crumb.title | h }}">{{ crumb.title | truncate: 24 | h }}</a>
 </li>
 {% endfor -%}
 <li class="active">{% block activebreadcrumb %}{{ title | h }}{% endblock %}</li>
</ul>

 

If you want to copy more than the ID - for example, Opportunity previously used "opptyId" and Products used "prodId", all stemming from an Account with "id" (account?id=AccountId&opptyId=OpportunityId&prodId=ProductId), then you can instead use the following

<ul class="breadcrumb">
 {% for crumb in page.breadcrumbs -%}
 <li>
  <a href="{{ crumb.url | append: request.query }}" title="{{ crumb.title | h }}">{{ crumb.title | truncate: 24 | h }}</a>
 </li>
 {% endfor -%}
 <li class="active">{% block activebreadcrumb %}{{ title | h }}{% endblock %}</li>
</ul>

Thanks Justin,

 

It doesn't work as expected. However I managed to get it work up to 3 levels, however after 4th level, I could only manage to go back to the previous level but not the previous parent. The reason that it wasn't working was the refid was missing in the fourth level.

 

Here is my code so far:

<ul class=breadcrumb>
    {% for crumb in page.breadcrumbs %}
       {% if request.query contains "refid" %}
           {% assign a = request.query | split: 'refid=' %}
           {% assign b = a[1] | split: '&refrel' %}
           {% assign refid = b[0] %}
           <li><a href="{{ crumb.url | append: '?id=' | append: refid }}" title="{{ crumb.title | h }}">{{ crumb.title | truncate: 24 | h }}</a>   </li> 
       {% else %}
           <li><a href={{ crumb.url | escape }}>{{ crumb.title | escape }}</a></li>
      {% endif %}
{% endfor %}

Any idea how to preserve the refId ?

 

Thanks,

Harry

Hi @harry_c2020,

It's easier to use the appropriate filters vs. split/append when you can - params.refid is how you would get the refid value, and then you can just re-use it. Similarly, typically avoid append (unless you know the URL is clean) and just use add_query. An example is {{ url | add_query: 'refid', params.refid }}. Consider the following changes - if you need refrel for anything, just use params.refrel (which is shorthand for request.params['refrel']

<ul class=breadcrumb>
    {% for crumb in page.breadcrumbs %}
       {% assign refid = request.refid %}
       {% if refid %}
           <li><a href="{{ crumb.url | add_query: 'id', refid }}" title="{{ crumb.title | h }}">{{ crumb.title | truncate: 24 | h }}</a></li> 
       {% else %}
           <li><a href="{{ crumb.url | escape }}">{{ crumb.title | escape }}</a></li>
      {% endif %}
{% endfor %}

If you can share an example URL (feel free to anonymize), it might be easier to help work through. Right now, all I know is that at some point you have a related record using refid and refrel would be the relationship schema between two entities, and when you go back one level you want to use the refid as the ID - is the reason you're splitting due to multiple layers of encoded refids?

Hi Justin,

 

Thanks for the response. it still doesn't work as expected.

I also need to change your code to 

request.params['refid'] instead of  request.refid to get the parameter value.
 
Here are the examples of the Url
home > Supplier details > Product
 
The refid refers to the Supplier id which is abc.
We can go back to Supplier details as the supplier id provided in the refid (abc) is correct. 
 
However if user go to another level (e.g product spec), the bread crumb would be
home > Supplier details > Product > Product Spec and its url is
 
The refid in the above query string now changed to def and it's the id of the product, but not the id of Supplier. We can go back to its immediate parent (Product) but when we try to go back to Supplier details, it gave an error 
An unknown failure has occurred. Error ID # [fff8d419-74dc-4a75-b683-7c344ea6b64d]
 
Maybe I am using the wrong approach. Any advice would be appreciated.
 
Thanks,
Harry

My apologies @harry_c2020, "request.refid" should have been "params.refid", as mentioned in the description above the code block.
Your explanation helps in describing the problem. This is because breadcrumbs are based on Web Page relationships, not entity relationships - all the breadcrumb code does is navigate through the hierarchy of Web Page links. In order for you to also maintain a history of the IDs related to those pages, your URL would need to grow exponentially.

Your best option is to use Liquid to retrieve attributes based on the breadcrumb loop's current page instead of relying on the URL for related records - e.g.:

<ul class=breadcrumb>
  {% if page.adx_partialurl == 'product-specification' %}
    {% assign prodId = params.refid %}
    {% assign prod = entities['new_product'][prodId] %}
    {% if prod and prod.new_accountid %}
      {% assign acctId = prod.new_accountid %}
    {% endif %}
  {% elsif page.adx_partialurl == 'product' %}
    {% assign prodId = params.id %}
    {% assign prod = entities['new_product'][prodId] %}
    {% if prod and prod.new_accountid %}
      {% assign acctId = prod.new_accountid %}
    {% endif %}
  {% endif %}
  {% for crumb in page.breadcrumbs %}
    {% assign bUrl = crumb.url %}
    {% if bUrl contains '/product/' %}
      {% assign bUrl = bUrl | add_query: 'id', prodId %}
    {% elsif bUrl contains '/account-maintenance-form/' %}
      {% assign bUrl = bUrl | add_query: 'id', acctId %}
    {% endif %}
    <li><a href="{{ crumb.url | truncate: 24 | escape }}">{{ crumb.title | escape }}</a></li>
  {% endfor %}

Note that this will require you to update the breadcrumb to add in additional branches for every subsequent child page/entity (replacing the first if to ensure it only triggers on the deepest child), and that this will work only for this particular hierarchy.

If you want to simplify things, change your various ID fields at the Entity Form level so that you don't have to change 'id', and can instead include them all - e.g. for account

justinburch_0-1600277008775.png

 

Hi Justin,

 

Thanks for the solution. It works as expected.

I'll try later to simplify things as you suggested.

 

Kind Regards,
Harry

Thanks @harry_c2020, feel free to respond here if you have more questions. If the above solution helped, please consider marking it as resolved so that other users can find the same solution more easily.

Hi Justin,

 

I couldn't see accept or resolve button so I couldn't mark it as resolved. I can only see "Like" and "Reply".

How do you accept it as a solution?

 

Thanks,
Harry

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results |Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 1: Community MembersSolutionsSuper UsersSolutionsPower Pages @Inogic  1   @ragavanrajan  2 @aofosu  1 @Jcook  1Open  @OliverRodrigues  1Open  @Lucas001  1Open Open    Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 2: Community MembersSolutionsSuper UsersSolutionsPower Pages @taraubianca25  2 @EmadBeshai  2 @ALP2  2@Fubar 2 @ekluth1  2@ragavanrajan 1 @mandela  1@OliverRodrigues 1 @Ajlan  1Open   @elishafxx  1    @TA_Jeremy  1    @helio1981  1       Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower PagesInogic2@EmadBeshai 6Ajlan1@ragavanrajan 4CraigWarnholtz1@Fubar 4  @Jcook 3  @OliverRodrigues2   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower PagesHenryed071Fubar3Inogic1OliverRodrigues2JacoMathew1EmadBeshai2faruk11  TA_Jeremy1   shubhambhangale1   doug-ppc1   hubjes1  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

  On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,100)