Sliding Panel Context is Lost

I am now trying to create a link on multiple images on a page.  I set the behavior  as a “Link” .  My interaction is a “Click”, then I toggle a sliding panel.  In the sliding panel is a “Page Include”,  The first picture has a query string “Id={{{$}}}”.  The second picture has a query string “Id={{{$}}}”.  The picture picture has a query string “Id={{{$}}}”.

When I click on any one of the three images, the correct sliding panel opens.  However, te same sliding panel data is opened regardless of the picture clicked.  I would think by passing Entity_01 or Entity_02 or Entity_03 it would open the related sliding panel.

First of all, congratulations on having a beautiful family. Those were not the pictures I was expecting to see when in Why_Work_List context.

It looks like it isn’t requerying. I don’t think sliding panels just naturally do that without being told to do that though. Have you tried making it so that upon clicking the children, this requeries the sliding panel? If so, what was your setup?

This also looks very related to which is resolved. Did Barry solve this for you there?

That works on a table list.  However, this is not a table list.  It is an image, inside the division of a response grid.  My picture interaction is “Click” toggle sliding panel.  In the sliding panel I have a page include “Id={{{$}}}”.  Entity_02 for the second image etc.  I would think it would pass the query string which is different for each picture.

Right, but just as it is with a table list, it would seem like you’d need to requery the model before reopening the sliding panel. Correct me if I’m wrong but wasn’t this the solution in the other thread:

My question to you is this: Are you requerying the model before reopening the sliding panel?


What happens if you put it before? I think it might be an order of operations thing. When you select the second, it would need to then be queried then opened. Rather than opened then queried.

I tried putting it before and then I tried before and after.  

Can you provide the XML to your setup using standard objects?

We do not use any standard objects.

Could you share what your interactions with each picture look like?

Thank for looking at this.  It happens here and another page that is not a table.  Here are the interactions

If you would do me a favor, open the page, put this in the console:‘WhyAm_UI’)[0]

See what it returns.
Press one of the pictures.
Repeat. See what it returns.
Press another one of the pictures.
Repeat. See what it returns.

Do they change?

Hello Stephen,

You will see it only returns something when the first one is clicked.

Almost. I’ll need you to press enter or return at the end of the string once at the beginning. Run your page by clicking one. Enter it again. Then press return. Then change to another picture. Press Return again.

What I’m after is the “a0J410000018oduEAA” down below. Yours will be unique. It should change from one picture to the next in order for a new page include to change.

What I’m more interested in is this:‘WhyAm_UI’)[0].PassId
which would return under‘WhyAm_UI’)[0]
except with less material.

This will verify whether or not the PassId is changing from one picture to the next.

What is before it in yellow probably doesn’t really matter at this point

Still nothing

Do you have anything return with‘WhyAm_UI’)[0] ? or even‘WhyAm_UI’) ?


That’s something! It’s totally working on that try.

When you press enter, the triangle to the left of “Object” is a dropdown that you can click to see more data. You can use it to explore what is currently in the model. I can also see that it changes after selecting an image. It adds PER_UI and Brick. We want to explore that dropdown to find the data in the Array position zero data.0.PassId
I’ve got a feeling that what is happening is that you successfully pass in the PassId for the first click on an image, but then it isn’t coming through after the second click.

We want to see if PassId = 1 on the first try and see if PassId = 2 on the second time. If it is 1 on the first and 1 on the second, then the setup isn’t right somewhere and diagnosing the problem becomes an entirely different ballgame. If it is 2 on the second, yet you see 1, then we likely have a bug that I need to show the developers.

This one is not as important as this one.  I turned this on in 2 weeks ago.  here is another page.