Get pointer to calling grid from UX in Tabbed_UI

[Peter.Greulich]

Grid_A calls UX_B. Both live in a Tabbed_UI. When I close UX_B I want to refresh Grid_A. How do I get a pointer to Grid_A?

FWIW: UX_B is not data bound so I can't use typical built in methods such as "open a UX to add a new record" or whatever.

[RichCPT]

Re: Get pointer to calling grid from UX in Tabbed_UI

var po = {dialog.object}.getParentObject();

[Peter.Greulich]

Re: Get pointer to calling grid from UX in Tabbed_UI

Thanks Rich. That doesn't seem to work in the context of a tabbed_ui. It works fine if you have a popup UX or some other variations.

[Peter.Greulich]

Re: Get pointer to calling grid from UX in Tabbed_UI

Upon further reflection maybe it can't because each tab is in its own iFrame. I know I got around this in the past by using the cursed & evil window variable. But I was trying to avoid that. Guess I'm just fooling myself.

[RichCPT]

Re: Get pointer to calling grid from UX in Tabbed_UI

It works for me and I am going three levels deep. Are you perhaps running one of the components in the "Home" tab? If so, that could be throwing things off. I do not know if the GetParentObject() works from subsequent tabs back to the "home" tab. The "Home" tab run in an iframe which creates a different 'window' global object.

If you need to get a pointer to something on the Home tab, from one of the other tabs, then you may have to put some code in the javascript component on the home tab to set a global variable to point to itself. Like in the 'onRenderComplete' for the component that is on the home tab:

window.parent.glb_Home_Cmpt = {Grid.object} // or
window.parent.glb_Home_Cmpt = {Dialog.Object}

On the other tabs you will be able to refer to 'window.glb_Home_Cmpt' or just 'glb_Home_Cmpt';

If that is not the problem then let's take a look at how you are refreshing the parent grid from the UX.
In my case I have two Grids (neither one on the Home tab) and the code is like this:

	var po = {grid.object}.getParentObject();    // Change to {Dialog.Object} if in UX
	//If this Grid does not have a parent then 'po' will be false. 
	if(po) {
	    if(typeof po.gridId != 'undefined') {
	    	// Called by a Grid
	    	var rowNum = po._selectedRow;
	    	po.refreshRow(rowNum);
	    }
	    if(typeof po.dialogId != 'undefined') {
	    	// TODO update UX component
	    }
	}

[RichCPT]

Re: Get pointer to calling grid from UX in Tabbed_UI

Well, we must have had the same thought about the iframe.
In my tabbedUI only the "Home" tab runs in an iframe, and it is easy to break out of that by inserting ".parent" after "window." references.

[RichCPT]

Re: Get pointer to calling grid from UX in Tabbed_UI

BTW, my code does not account for the fact that the user may have switched back to Grid_A and changed the selected row number. If they did then the row they really changed will not get updated - on screen.

[Peter.Greulich]

Re: Get pointer to calling grid from UX in Tabbed_UI

You're right Rich, it does work. Thanks. I built a simple demo and it works there. Now I have to go back to figure out why my more complex real world attempt failed.