Topic
  • 4 replies
  • Latest Post - ‏2017-06-07T12:43:33Z by Owais27
Owais27
Owais27
12 Posts

Pinned topic Report Portal Section just keeps loading

‏2017-06-06T13:54:02Z | portal section

We are currently at TRIRIGA version 10.5.1/3.5.1.1

 

In the Navigation Pages if a particular Portal section with a report, has a result set of more than the property "Max Records Displayed", then the results are not shown, and the section just keeps loading as show in the attached pic.

 

This behavior is not the case if the results returned are within the limit set in the portal section. Also, when the section is maximized we can see all the results too.

 

It works in the case of a hierarchy query too

  • Casey Cantwell
    Casey Cantwell
    177 Posts
    ACCEPTED ANSWER

    Re: Report Portal Section just keeps loading

    ‏2017-06-06T15:54:01Z  
    • Owais27
    • ‏2017-06-06T15:45:54Z

    Hi Casey,

     

    The Issue you have mentioned is that the Portal Section displays all the records from the report ignoring the max record parameter.

     

    But, we have a different issue, were the report displays fine if the record result count is lesser than the max record parameter, and just keeps loading if the record count is more than the max record parameter.

    I believe the fix I note, will resolve your problem.  Queries are returning the entire result set in 3.5.1.1, and not stopping at the max count.  My recommendation is to upgrade to the the fix pack with this fix, and see where you stand after that.

    Updated on 2017-06-06T15:54:11Z at 2017-06-06T15:54:11Z by Casey Cantwell
  • Casey Cantwell
    Casey Cantwell
    177 Posts

    Re: Report Portal Section just keeps loading

    ‏2017-06-06T15:41:13Z  

    We had a defect / APAR where the max record displayed parameter was being ignored, and the entire result set was being pulled back.  The issue is resolved in 3.5.1.2, and 3.5.2.2.

     

    Here is the release note on the issue:  Portal section queries display the maximum results that are specified in the Portal Builder. (Tri-237640-IV87771)

  • Owais27
    Owais27
    12 Posts

    Re: Report Portal Section just keeps loading

    ‏2017-06-06T15:45:54Z  

    We had a defect / APAR where the max record displayed parameter was being ignored, and the entire result set was being pulled back.  The issue is resolved in 3.5.1.2, and 3.5.2.2.

     

    Here is the release note on the issue:  Portal section queries display the maximum results that are specified in the Portal Builder. (Tri-237640-IV87771)

    Hi Casey,

     

    The Issue you have mentioned is that the Portal Section displays all the records from the report ignoring the max record parameter.

     

    But, we have a different issue, were the report displays fine if the record result count is lesser than the max record parameter, and just keeps loading if the record count is more than the max record parameter.

  • Casey Cantwell
    Casey Cantwell
    177 Posts

    Re: Report Portal Section just keeps loading

    ‏2017-06-06T15:54:01Z  
    • Owais27
    • ‏2017-06-06T15:45:54Z

    Hi Casey,

     

    The Issue you have mentioned is that the Portal Section displays all the records from the report ignoring the max record parameter.

     

    But, we have a different issue, were the report displays fine if the record result count is lesser than the max record parameter, and just keeps loading if the record count is more than the max record parameter.

    I believe the fix I note, will resolve your problem.  Queries are returning the entire result set in 3.5.1.1, and not stopping at the max count.  My recommendation is to upgrade to the the fix pack with this fix, and see where you stand after that.

    Updated on 2017-06-06T15:54:11Z at 2017-06-06T15:54:11Z by Casey Cantwell
  • Owais27
    Owais27
    12 Posts

    Re: Report Portal Section just keeps loading

    ‏2017-06-07T12:43:33Z  

    I believe the fix I note, will resolve your problem.  Queries are returning the entire result set in 3.5.1.1, and not stopping at the max count.  My recommendation is to upgrade to the the fix pack with this fix, and see where you stand after that.

    Thanks Casey.

     

    We validated the issue in 3.5.1.3 and it works as expected.