Hi Team,
I need help refreshing parameter values in a view.
I have View A and View B, both of which accept an input parameter (e.g., LoadID).
When View B loads, it reads values from the database, and when navigating from View A I use:
system.perspective.navigate("ViewA", params={"LoadID": 1})
This correctly updates the parameters for both views.
However, I now have View C, which displays View B using an Embedded View component. In this case, View A is no longer involved, so I don’t want to navigate through View A.
I am assigning database values directly to the parameters of View B, but the parameter does not refresh—it keeps the previous LoadID value.
What can I do to properly refresh the parameter value of View B when it is embedded inside View
I think you need to show the code you are using for the embedded view, and whatever it is you are using to show that the parameter value isn’t changing. A view parameter doesn’t require refreshing, but whatever bindings or scripts you’re using to either pass it or receive and display it might.
Make view C perform the parameter updates to its embedded view B.
this is View under last tab unload I am opening the unload view.
1st rack will be selected then as per rack selection load Id should populate.
I have one messagehandler on ‘unload view’ which gets the loadId from DB and sets to params
How to update params from View C?
By creating same message handler and prams on view C?
self.view.params.loadId=loadId
That is setting the view’s own parameter. Are you wanting that parameter to propagate UP into the view that is embedding it? If so you need to make sure it is set as a bidirectional parameter. But I’m still confused as to what exactly you’re trying to do. You have system.perspective.navigate() highlighted, and yet commented out…?
yes, it is bidirectional.
I don’t want to navigate to loads view as it is no longer involved so commented out.
View C needs to query the database and store the value in a custom property.
The query needs to be triggered any time the Load ID changes. I would venture to guess you probably already have some sort of event occurring elsewhere in the system that changes the Load ID.
You may also want to consider storing the Load ID in a memory tag or session.custom.prop and just bind View A, B, and C to that value. This way you have a single value accessible from anywhere.
