RefreshListData Dynamic Panels

[rgibson]

I have a MainUX, CustomerListUX with a list control and a CustomerDetailsUX.

Both the CustomerListUX and the CustomerDetailsUX open up the in a dynamic panel within a navigator panel on the MainUX. The end user finds the customer in the customer list and double click on the customer record to open the customer details UX.

Without going into why I'm not using the List Details....what I need to do is....

After the user edits a record and submits it on the CustomerDetails dynamic panel I want to refresh the data in the CustomerList control in the other dynamic panel. So, when the user clicks on the submit button I have...

var panelName = "A" + {dialog.object}.getValue('FID'); //this is the customer details dynamic panel name
var po = {dialog.object}.getParentObject(); //pointer to the parent UX
var cPanel = po.panelGet('ALIAS_CUSTOMERLIST'); //this is the name of the CustomerList dynamic panel. This isn't working.

{dialog.object}.submit();
cPanel.refreshListData('CUSTOMER_LIST', keepFocusOnCurrentSelection); //this doesn't work. I've also tried po.refreshListData
po.panelRemove('PN_CONTENT',panelName,'name'); //this works.

[peteconway]

I have to ask - why put yourself through the agony of dealing with Dynamic Panels just because you can? When the UX goes through the initial loading and rendering it's is aware of all controls in its state - lets call it it's environment, where everything is known. When you introduce new things to the environment, it's compromised and needs to deal with something new that it has little to no knowledge of, and so you then need to find work arounds to translate to the environment what should happen, and then you introduce another new thing and want the environment to manage how those two thing work together with the environment as a translator, it just does not make sense to me. So what is the solution - well the quickest way is to create two Panel Cards that are called say Host1 and Host2, now the environment is awaree, no surprises, you can then load whatever number of other controls in tho those cards as much you want, you can then easily manage anything in those cards both in and out by using the getParent getChild action Javascript.
Hope this helps.
Pete

[rgibson]

I liked the way the dynamic panels could be opened multiple times so I could open multiple customers and multiple bookings at the same time in tabs and title them appropriately. I do agree though that this is becoming a little frustrating.

[peteconway]

If that's what you are wanting Target Window - turn off Use cache UX Component, make certain re-use existing window is UN CHECKED - read the smart field notes on Window Name click the ... this is key to control also look up destroy to remove a window from the DOM, don't set any window height or width, let it be inherited from the incoming UX, you can then have a many of those as you want and have access to the parent child functions.
Good luck.

[peteconway]

If you are wondering why its ok to use Windows and not dynamic Panel Cards, the Window sits on top of the application in its own space in the DOM and does not have to integrate or interact with other Panel Controls. In other words is less complicated.
Pete