Prev
Next
Forums Lawson Design Studio

Portal Page Load Time

Sort:
You are not authorized to post a reply.
Author
Messages
Ken Ptak
Basic Member
Posts: 20
Basic Member
10/28/2008 6:34 PM
    I am trying to create a Portal Page that will list all of our Accounting Units, AU Description, and AU Status from the GLNAMES table. The goal of this page will be to allow the user to perform a search (CTRL+F).  In order to accomplish this, I need to have the portal page populate every AU on a single page (No next/previous).

    Our users will be able to search by either the Accounting Unit or a description of the AU. We do not want to grant GL20 access to all users, we want this to be an all inclusive list to be placed on a General dashboard for easy access.
     
    I’ve created a Portal Page with the following Data Query API:
     
    /servlet/Router/Data/Erp?PROD=DE1&FILE=GLNAMES&FIELD=ACCT-UNIT;DESCRIPTION;ACTIVE-STATUS;&OUT=XML
     
    When I have the Max Records=25 and Page Size=25 and I ‘Preview’ the page, it instantly loads.
     
    When I increase the Max Records and Page Size to 18000 (we have approx 17500 records in GLNAMES), the preview takes well over 10-15 minutes to load.
     
    Any suggestions on how to increase the response time and/or alternate ways to produce this all inclusive list for all users?
     
    Thanks for your time,
    Ken
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    10/29/2008 11:42 AM
      If the purpose of performing your DME is to make it quicker for users to find the Accounting Unit information you have found the obvious flaw by trying to load all of the records and then use Ctrl-F to search on that page of records.
      I am guessing just using Lawson drill around function doesn't provide you with all of the information in a single display and that's why you don't just give the user Inquire access to the Portal form.
      Why not create a search page for the user to enter the data they want and only query matching records for display?
      David Williams
      John Henley
      Senior Member
      Posts: 3348
      Senior Member
      10/29/2008 7:00 PM
        The OUT=XML on a DME is a memory killer for large data sets. Perhaps you might think about doing this a different way. For example, you could create a static page and use a URL instead of a DME. In other words, why load it from the database every time a user requests the page? You could put the page generator into a scheduler (i.e. generate it from a script and use jobschd or from ProcessFlow and use ProcessFlow scheduler). If you wanted to get *really* ambitious, create a processflow service/trigger in Design Studio that triggers every time GL20 updates are done.
        Thanks for using the LawsonGuru.com forums!
        John
        You are not authorized to post a reply.