Page Layout Builder - Linking property issues

[dickerman7239]

In the Page Layout Builder I have a master grid component and it children, each in their own Tab Pane. I want to link the children to the master for navigation and I have tried both the Link and Base Filter Grid Definition properties to attempt this.

I've followed Video 38, Using Arguments in the Page Layout and TabbedUI Components to Filter Records - A5 Web Application Features with no luck. As in the video, after declaring the variable and binding the argument to the variable... when clicking the tab for the child, instead of getting the filtered records the table comes back with "No records in query."

I do not want to use the Linked Grids in the Grid Component method because it forces the tabbed grid to the right or beneath the master grid. Keeping the tabs on the master grid is very clean and first choice. Any ideas on making this work or trouble shooting would be appreciated. Kim D.

[Selwyn Rabins]

Re: Page Layout Builder - Linking property issues

In the Page Layout Builder I have a master grid component and it children, each in their own Tab Pane. I want to link the children to the master for navigation and I have tried both the Link and Base Filter Grid Definition properties to attempt this.

I've followed Video 38, Using Arguments in the Page Layout and TabbedUI Components to Filter Records - A5 Web Application Features with no luck. As in the video, after declaring the variable and binding the argument to the variable... when clicking the tab for the child, instead of getting the filtered records the table comes back with "No records in query."

I do not want to use the Linked Grids in the Grid Component method because it forces the tabbed grid to the right or beneath the master grid. Keeping the tabs on the master grid is very clean and first choice. Any ideas on making this work or trouble shooting would be appreciated. Kim D.

i don't really understand what you are trying to do, but i can tell you that the page layout component is not designed to allow you to link two grids in a parent-child manner.

if you want to link two or more grids in a master - child relationship, then you must use Linked Content Sections in the master grid.

video 38 is not a demonstration of how to link grids in a parent-child manner. it is a demonstration of how the grids on a page Layout component can be filtered based on the value of an argument.

you say that you don't want to use linked grids in the Grid component because that forces your to put the child grid underneath or to the right of the master grid.

but, actually this is not entirely correct. you can put the linked grids in the Master Template. the master template can have tab panes. so you can design a Master Template with tab panes and then put the linked grid in one of the tabbed Panes.

[dickerman7239]

Re: Page Layout Builder - Linking property issues

First: Please see attached for what I wanted to do; having the grids linked for the purpose of navigation (filtering) and for auto insert of linked field content for new record insert...

if you want to link two or more grids in a master - child relationship, then you must use Linked Content Sections in the master grid...

...you can put the linked grids in the Master Template. the master template can have tab panes. so you can design a Master Template with tab panes and then put the linked grid in one of the tabbed Panes.

I did try this solution and was able to produce a master grid with 3 tabs. For my skill level, the best I was able to do was get all of my tabs into one of the Master Temp tabs (as you indicate above), but that is not acceptable and all the queries failed. Looking at the xbasic, html, and javascript it appears you are limited to 3 tabs going this direction, is that true?

I did experiment by separating the linked grids into separate Linked Component parts and tried to produce more tabs with the html and javascript but was not able to prevail. At this point it seams my choices:

1. Creaate additional tabs in Master Template. This would require confirmation that is doable and the knowledge source transfer.

2. Settle for a tabbed linked grid in the lower freeform edit region.

3. Settle for a tabbed row expander.

4. Create separate pages for the other grids and navigate to them via navbar and/or button while filtering.

5. Lastly and maybe most appealing... continue to work on this in the garage with the door closed and car running.

Please let me know if I am wrong on the Master Template limitations above. Thanks in advance. Kim D.

[dickerman7239]

Re: Page Layout Builder - Linking property issues

Selwyn:
A second question specific to the Page Layout Builder and Video 38... If I understand your response points, the video is a demo on filtering grids that have already been linked via the grid builder. Had I linked my tables in the parent grid and placed them in the Master Template or Free Form areas, I should get the same response via the use of the argument. My question: In the page layout builder, the properties of the inserted grid component inlcude: LINK, Filter (Vid38), and Order. It appears that you should be able to LINK a target grid via an argument as well. What is this LINK function for? KimD.

[QUOTE=Selwyn Rabins;546340] ...video 38 is not a demonstration of how to link grids in a parent-child manner. it is a demonstration of how the grids on a page Layout component can be filtered based on the value of an argument...QUOTE]

[Selwyn Rabins]

Re: Page Layout Builder - Linking property issues

First: Please see attached for what I wanted to do; having the grids linked for the purpose of navigation (filtering) and for auto insert of linked field content for new record insert...



I did try this solution and was able to produce a master grid with 3 tabs. For my skill level, the best I was able to do was get all of my tabs into one of the Master Temp tabs (as you indicate above), but that is not acceptable and all the queries failed. Looking at the xbasic, html, and javascript it appears you are limited to 3 tabs going this direction, is that true?

I did experiment by separating the linked grids into separate Linked Component parts and tried to produce more tabs with the html and javascript but was not able to prevail. At this point it seams my choices:

1. Creaate additional tabs in Master Template. This would require confirmation that is doable and the knowledge source transfer.

2. Settle for a tabbed linked grid in the lower freeform edit region.

3. Settle for a tabbed row expander.

4. Create separate pages for the other grids and navigate to them via navbar and/or button while filtering.

5. Lastly and maybe most appealing... continue to work on this in the garage with the door closed and car running.

Please let me know if I am wrong on the Master Template limitations above. Thanks in advance. Kim D.

there are no limitations of any kind on the complexity of the master template. you can have as many tabs as you want and you can put any content that you want in the tab panes.

this video shows and example of how to put the linked content into a tab pane.

http://screencast.com/t/NDY4NDg0YmE

[Selwyn Rabins]

Re: Page Layout Builder - Linking property issues

[QUOTE=dickerman7239;546442]Selwyn:
A second question specific to the Page Layout Builder and Video 38... If I understand your response points, the video is a demo on filtering grids that have already been linked via the grid builder. Had I linked my tables in the parent grid and placed them in the Master Template or Free Form areas, I should get the same response via the use of the argument. My question: In the page layout builder, the properties of the inserted grid component inlcude: LINK, Filter (Vid38), and Order. It appears that you should be able to LINK a target grid via an argument as well. What is this LINK function for? KimD.

...video 38 is not a demonstration of how to link grids in a parent-child manner. it is a demonstration of how the grids on a page Layout component can be filtered based on the value of an argument...QUOTE]

let me try to rephrase what video 38 is showing.

say you put a grid (customerGrid) on a Page Layout component.
you then define an argument for this PageLayout component called ':whatState' and you bind this argument to a session variable called 'session.whatstate'.

you can then either filter or link the customerGrid and use the argument in the filter or link.

so your filter might be

state = :whatstate

in this case if session.whatstate is 'ma', then when you open the page that contains the PageLayout component the grid will only show customers in 'ma'. since this is a filter, when you add a new customer, you will be free to set the state for this new record to any state that you want.

on the other hand, had you defined a link (not a filter) and the link had linked the 'state' field in the grid to the ':whatstate' argument, when the page that contained the pageLayout was opened the grid would only show records were the state was 'ma' (just like the case where the grid was filterd). HOWEVER (and this is the key difference between linking and filtering), when you added a new record, regardless of what value you entered into the state field, when the record was saved, the state would be automatically set to 'ma'.

now, the 'customerGrid' that you placed on the pageLayout component might have defined a Linked Content section that showed orders for the current customer.

in this case, every time you click on a different row in the Grid component, the related records in the orders grid would be shown.

so, the ONLY way to show records in a child grid that are related to records in a parent grid is to define a linked content section in the parent grid.

i hope that this is helpful.

[dickerman7239]

Re: Page Layout Builder - Linking property issues

Selwyn: Thank you for the response and video it was most helpful. Based on your video I did everything right but still had issues. To start with a clean slate I recreated the master grid and repeated my attempt to established linked grids with tabs. Like before, I can get the tabs to appear but not work. My results:

I have tabs but when I click on them the grids appear with "No records in query."

Also, after linking the grids and modifying the master template the following functions do not work:

Detail View (method of display = double click on row) fails. Gives an error message of: 'this._originalIDVValues[...].length' is null or not an object.

Other layout options such as the Highlight row on hover, Highlight row on select, and Has row seletor column all no longer function and appear. I check all this functionality prior to linking the grids.

One difference you will see in my code is that I created multiple linked content sections to test the ability of creating more than 3 tabs.

Here is my code:
My HTML
<!--IMPORTANT: If you remove a tab pane from the HTML markup, be sure -->
<!--to also make the necessary changes in the associated Javascript -->

<!--Tab Container - Tabs on Top -->

<div id="{tabId}">
<div id="{tabId}.TABBAND">
<a id="{tabid}.0.TAB" class="" href="#">Main View</a>
<a id="{tabid}.1.TAB" class="" href="#">Managers</a>
<a id="{tabid}.2.TAB" class="" href="#">Locations</a>
<a id="{tabid}.3.TAB" class="" href="#">Contacts</a>
<br style="clear: both;" />
</div>
<div id="{tabId}.PANES">
<div id="{tabid}.0.PANE">
{grid.Search_Part}
{grid.Grid_Part}
</div>

<div id="{tabid}.1.PANE">
{LinkedContentSection:MANAGER}
</div>

<div id="{tabid}.2.PANE">
{LinkedContentSection:LOCATIONS}
</div>

<div id="{tabid}.3.PANE">
{LinkedContentSection:CONTACTS}
</div>
</div>
</div>


My JavaScript
window['{tabid}Obj'] = new A5.Tab('{tabid}',[
{html: 'Main View', value: 'Main View' },
{html: 'Managers', value: 'Managers' },
{html: 'Locations', value: 'Locations' },
{html: 'Contacts', value: 'Contacts'}
],{
tabClassName: 'A5TabTopOff',
tabSelectedClassName: 'A5TabTopOn',
tabDisabledClassName: 'A5TabTopDisabled',
paneClassName: 'A5TabTopPane'
});

I'm a bit stumped. KimD.

[Selwyn Rabins]

Re: Page Layout Builder - Linking property issues

Selwyn: Thank you for the response and video it was most helpful. Based on your video I did everything right but still had issues. To start with a clean slate I recreated the master grid and repeated my attempt to established linked grids with tabs. Like before, I can get the tabs to appear but not work. My results:

I have tabs but when I click on them the grids appear with "No records in query."

Also, after linking the grids and modifying the master template the following functions do not work:

Detail View (method of display = double click on row) fails. Gives an error message of: 'this._originalIDVValues[...].length' is null or not an object.

Other layout options such as the Highlight row on hover, Highlight row on select, and Has row seletor column all no longer function and appear. I check all this functionality prior to linking the grids.

One difference you will see in my code is that I created multiple linked content sections to test the ability of creating more than 3 tabs.

Here is my code:
My HTML
<!--IMPORTANT: If you remove a tab pane from the HTML markup, be sure -->
<!--to also make the necessary changes in the associated Javascript -->

<!--Tab Container - Tabs on Top -->

<div id="{tabId}">
<div id="{tabId}.TABBAND">
<a id="{tabid}.0.TAB" class="" href="#">Main View</a>
<a id="{tabid}.1.TAB" class="" href="#">Managers</a>
<a id="{tabid}.2.TAB" class="" href="#">Locations</a>
<a id="{tabid}.3.TAB" class="" href="#">Contacts</a>
<br style="clear: both;" />
</div>
<div id="{tabId}.PANES">
<div id="{tabid}.0.PANE">
{grid.Search_Part}
{grid.Grid_Part}
</div>

<div id="{tabid}.1.PANE">
{LinkedContentSection:MANAGER}
</div>

<div id="{tabid}.2.PANE">
{LinkedContentSection:LOCATIONS}
</div>

<div id="{tabid}.3.PANE">
{LinkedContentSection:CONTACTS}
</div>
</div>
</div>


My JavaScript
window['{tabid}Obj'] = new A5.Tab('{tabid}',[
{html: 'Main View', value: 'Main View' },
{html: 'Managers', value: 'Managers' },
{html: 'Locations', value: 'Locations' },
{html: 'Contacts', value: 'Contacts'}
],{
tabClassName: 'A5TabTopOff',
tabSelectedClassName: 'A5TabTopOn',
tabDisabledClassName: 'A5TabTopDisabled',
paneClassName: 'A5TabTopPane'
});

I'm a bit stumped. KimD.

you should try to copy the example i make in the video exactly. make sure you can get that working.
since we know that it does work (as my video shows), then if you can't get it working, you know the problem is in your code somewhere.

once you have gotten my example working, then you have a safe jumping off point for your own customization. you can customize one small thing at a time and keep checking that it is still working.

that's a much easier approach than making wholesale changes and then trying to figure out why it does not work.

[dickerman7239]

Re: Page Layout Builder - Linking property issues

Selwyn, Very good advice.

Here are the steps for the test.

1. I stripped everything out and started at the beggining, first individually testing each component, all is well.

2. After linking the grids and placing in master template as in the video's starting point, all master grid functionality is as it should be, linked grids are functioning, all is well.

3. Followed the video verbatim using the tab on top master template, all is well. I now only have 2 tabs but working as in video.

4. Advancing, I added two more grids to the EXISTING linked grids section, all is well.

5. Adding a second linked content section and placing it into a 3rd tab... BROKEN. All earlier issues resurfaced.

6. Repeated the above steps... results consistant.

It seems you can not have more than one linked grid section with this method for creating tabs. To have multiple grids hiding in one linked section placed in a tab probably isn't the best UI design.


This brings me back to my original statement of not being able to have more than 3 functioning tabs. If you place the search and grid on the first tab, place your linked content section on the second, and you cannot add additional linked content... giving the detail view to the 3rd tab, you're limited to 3 tabs.

This is why I attempted doing this with the page builder. It is very easy to place the grids in their own tabbed pane, if I could get the linking to work I'd be in good shape.

What would be the next step? Again, many thanks for the interaction and help. KimD.

[Selwyn Rabins]

Re: Page Layout Builder - Linking property issues

I have taken the example I did yesterday further in this video:

http://screencast.com/t/M2M2YjIwZTU

this example shows two different linked content sections, each in their own tab.

[dickerman7239]

Re: Page Layout Builder - Linking property issues

Selwyn:
I tested again this morning with fresh grids and for simlicity sake used your names for the new linked content sections of XX and YY respectively. Stepped through the process, all worked fine with XX only. Again, all issues resurfaced once I inserted the the 2nd linked content section YY.

I have now reproduced this same result multiple times on 3 separte sets of grids. I am on build 3040_3571 should I try to reinstal latest patches? KimD.

[Selwyn Rabins]

Re: Page Layout Builder - Linking property issues

Selwyn:
I tested again this morning with fresh grids and for simlicity sake used your names for the new linked content sections of XX and YY respectively. Stepped through the process, all worked fine with XX only. Again, all issues resurfaced once I inserted the the 2nd linked content section YY.

I have now reproduced this same result multiple times on 3 separte sets of grids. I am on build 3040_3571 should I try to reinstal latest patches? KimD.

i can't say why it is that when you try to follow the example I show (which of course works), it does not work in your case. I don't think that this has anything to do with what release you are on.

there has to be something that you are not following correctly.

the grids i build were on the invoice_header and invoice_items tables from alphasports (.dbf tables).

if you construct your own test case using these two tables and then send me what you have built, I will be able to see where you have gone wrong.

[dickerman7239]

Re: Page Layout Builder - Linking property issues

Selwyn: I agree with you that it should work as your example... I haven't been able to identify any differences between the example and my project.

I will need to set AlphaSports to test... I am working in MySQL/AlphaDAO which I would think would not be the issue, any known challenges?

[dickerman7239]

Re: Page Layout Builder - Linking property issues

Selwyn: I set up the same test in AlphaSports and received same response as in my project.

My HTML:
<!--IMPORTANT: If you remove a tab pane from the HTML markup, be sure -->
<!--to also make the necessary changes in the associated Javascript -->

<!--Tab Container - Tabs on Top -->

<div id="{tabId}">
<div id="{tabId}.TABBAND">
<a id="{tabid}.0.TAB" class="" href="#">Search and Grid</a>
<a id="{tabid}.1.TAB" class="" href="#">Linked Content1</a>
<a id="{tabid}.2.TAB" class="" href="#">Linked Content2</a>
<br style="clear: both;" />
</div>
<div id="{tabId}.PANES">
<div id="{tabid}.0.PANE">
{grid.Search_Part}
{grid.Grid_Part}
</div>

<div id="{tabid}.1.PANE">
{LinkedContentSection:XX}
</div>

<div id="{tabid}.2.PANE">
{LinkedContentSection:YY}
</div>
</div>
</div>


My JavaScript:
window['{tabid}Obj'] = new A5.Tab('{tabid}',[
{html: 'Search', value: 'Search' },
{html: 'Grid', value: 'Grid' },
{html: 'Detail View', value: 'Detail View'}
],{
tabClassName: 'A5TabTopOff',
tabSelectedClassName: 'A5TabTopOn',
tabDisabledClassName: 'A5TabTopDisabled',
paneClassName: 'A5TabTopPane'
});

[steinmanal]

Re: Page Layout Builder - Linking property issues

I am trying to create tabbed linked content by modifying the master layout template.

I insert the linked content into the DIV container for the appropriate TAB.

When I preview the tab in the grid, it doesn't display the linked content. Instead it displays the placeholder for the grid (e.g."{LinkedContentSection:CONTACT}".

Can someone help me understand what I might be doing wrong?

Thanks.

Alex