Hi,

I promise this is the simplest example I could make that recreates the behavior .. smile.

I'm trying to create a web page with a paged table in the top half and some detailed content in the lower half which is based on the selected row from the table.

To separate and compartmentalize behaviors, I architected as:
    PROTOCOLTOP:
        main wrapping protocol
        recovers/stores all data for all possible table pages via "Data to JSON" component
        contains controls for paging
        contains Dynamic Content Container to house output of single-page table-generating protocol
        as dictated by paging behavior, will send the appropriate JSON-data slice to the single-page table-generating protocol to generate the table page content
        
    PROTOCOLMIDDLE:
        single-page table-generating protocol
        generates a single-page table based on JSON provided to it
        contains a Data Connector so that selected rows from the table will trigger population of its own Dynamic Content Container
        contains a Dynamic Content Container to house output of detail-generating protocol 
    
    PROTOCOLBOTTOM:
        generates detail content based on Data-Connector action from PROTOCOLMIDDLE
        
I've attached each protocol (protocols.zip).  To stitch them together...
    In PROTOCOLTOP, Protocol Function (start of pipe 3) should be calling PROTOCOLMIDDLE.
    In PROTOCOLMIDDLE, Protocol Function (start of pipe 4) should be calling PROTOCOLBOTTOM.
    In PROTOCOLBOTTOM, "download request link" (2nd component, pipe 1) should have Protocol Link populated with PROTOCOLBOTTOM (the specific protocol is arbitrary and won't ever get called .. here, simply to trigger the reported behavior for this post)

Everything nicely works as expected, _UNLESS_ PROTOCOLBOTTOM contains a Protocol Link (or an Input Form).  If it does contain a Protocol Link, the following steps will generate an onLoad error/alert:
    1) Run PROTOCOLTOP.
    2) Select any table row, which should display the detail content below the table.
    3) Click on the "next" page control to move to the second page of the table.
    4) Select any table row, which should display the detail content below the table.  However, it should also display an alert indicating "Errors detected while calling onLoad functions in report."  I've attached a screenshot.

I haven't been able trace-down or resolve the alert, but it seems related to the page trying to intialize the protocol link generated by PROTOCOLBOTTOM and being unable to find the shim gif.

I did try removing \$(RunId) from PROTOCOLTOP and PROTOCOLMIDDLE's Protocol Function Application ID setting, but that has not helped.

Is this alert expected?  Is there a way to prevent it?  Is something not set up correctly in the protocols?

Thanks for any expert guidance.

Best,

Andrew