How to share data between web pages in the Power Pages Site

[KAVINASHB]

Hi,

There is a requirement where when user lands on homepage then user will select a plan from a list. Based on selected plan, I need to filter the data in other web pages. I'm trying to use session storage but web page has fetchxml query which is getting executed first before I use the session storage. Please suggest approach on this

[OliverRodrigues]

Hi, once a user selects a Plan, do you want to show another list with related data, is that the requirement?

If that's the case you should be looking at adding a subgrid to the form, let us know if you need help with this.

[KAVINASHB]

Hi @OliverRodrigues ,

Home page will show list of Plans . When user selects a Plan called "A", user will get redirected to another Page called Details. This Page should show the data based on Plan selected - "A". There are 6 or 7 other pages where I need to Filter the data based on the Plan - "A". How can I achieve this? Please suggest. All pages having custom design using bootstrap.

[Fubar]

---

@KAVINASHB wrote:

All pages having custom design using bootstrap.

---

Without more detail this makes it unclear what the answer would be.

Generally speaking, the Form (e.g. Basic Form) has settings (Record Source Type) to receive the GUID of the record it needs to work with - by default this is usually via a url parameter named 'id' but can be configured to be a different name.

A List will send the GUID of the record to the respective page (e.g. via the Options grid), again by default this will be a url parameter named 'id' but can be configured to be different.

Similarly, in Liquid you can retrieve url parameters from the liquid request object

https://learn.microsoft.com/en-us/power-pages/configure/liquid/liquid-objects#request

Depending on exactly what you are doing and what customization you are performing will determine the HOW to do what you need but basically you will add url paramater that is the guid of the record you are working with and pass it to the next page, and on that page retrieve the guid (much of which is just configuration if using standard elements/components, but depending on your customization could be Liquid and or JavaScript)

[KAVINASHB]

Thanks for your response. We are not using any standard elements and it will be customized bootstrap centric design and need to display data from different entities based on Plan. If we go for Query Param.. how do I update Query Param for each page? User will select a plan then navigates to details page .. here we can we pass the ID.. after that user can navigate to any other page using Global Nav. How can it be achieved? We would like to use fetchxml to get data from different entities.

[OliverRodrigues]

If we go for Query Param.. how do I update Query Param for each page?

Once users select the Plan, you should have the Plan ID, when rendering the liquid for each page, you should include the Plan ID

for example:

<a href="/mypage01?planid={{Request.params.planid}}">my page 01</a>

User will select a plan then navigates to details page .. here we can we pass the ID.. after that user can navigate to any other page using Global Nav. How can it be achieved?

Do you mean that users will select a separate link, not related to the first page, and the Portal should still know what Plan they have selected?

[KAVINASHB]

Hi @OliverRodrigues , That's right. Once they navigate to first page, user will select any other page in the Global navigation menu. We should know the plan in that case as well. Please suggest

[OliverRodrigues · Accepted solution]

I would achieve this via the following logic:

• Plan should be a Lookup (or optionset) field within the Contact record
• Basic Form so user selects the Plan
• Every other form / page that needs this, can retrieve the value via Liquid using the User object {{ user.<myplanfield> }}
• then you can do whatever logic you need 

[KAVINASHB]

@OliverRodrigues any other way we can achieve it without using OOTB components?

[OliverRodrigues]

if your additional pages are using OOB lists, you may be able to leverage the "Metadata Filter" for example.

But it seems that you want to use fetch/custom HTML anyway for the additional pages, so I guess my solution is the most OOB way that I can think of anyway

hope this helps