Page Breaking Bug: loadAllRemainingRecords and loadNextOffsetPage not working

  • 1
  • Question
  • Updated 2 days ago
  • In Progress
Platform: Skuid On Salesforce
Version: 12.0.4
Browser: Chrome (71.0.3578.98)
OS: Windows 10 (64 Bit)

loadNextOffsetPage is not working, both in Javascript as well as when you press the "Load more" button on the bottom of a table.

This is probably related to loadAllRemainingRecords not working.

The symptoms are:

When loadNextOffsetPage is called, it finishes processing but does not load any more records when there are more records to load.

When loadAllRemainingRecords is called, it never finishes processing.

Below is a page where you can reproduce the issue. You'll need to replace the name conditions on the Account model with the names of two accounts you know you have in your system.

When pressing the "Load All Accounts" you'll see it blocks the ui and never unblocks.

When pressing "Load Next Account" it will block the ui, then unblock, but will not add another row into your model.

When pressing "Load more" at the bottom of the table it will block the ui, then unblock, but will not add another row into your model.

<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" showheader="true">
<model id="Account" limit="1" query="true" createrowifnonefound="false" datasource="salesforce" sobject="Account">
<field id="Id"/>
<field id="Name"/>
<condition type="multiple" value="" field="Name" operator="in" enclosevalueinquotes="true">
<value>User Account</value>
<buttonset model="Account" uniqueid="sk-3Yd8-245">
<button type="custom" label="Load All Accounts" uniqueid="sk-3Ydo-353" snippet="loadAllRemainingAccounts"/>
<button type="custom" label="Load Next Account" uniqueid="sk-3Yec-381" snippet="loadNextAccount"/>
<skootable showconditions="true" showsavecancel="false" showerrorsinline="true" searchmethod="server" searchbox="false" showexportbuttons="false" hideheader="false" hidefooter="false" pagesize="10" alwaysresetpagination="false" createrecords="false" model="Account" buttonposition="" mode="readonly" allowcolumnreordering="false" responsive="true" uniqueid="sk-3YcA-107" emptysearchbehavior="query">
<field id="Id" hideable="true" uniqueid="fi-3YcD-124"/>
<field id="Name" hideable="true" uniqueid="fi-3YcD-125"/>
<massactions usefirstitemasdefault="true"/>
<jsitem location="inlinesnippet" name="loadAllRemainingAccounts" cachelocation="false">skuid.$.blockUI();
    finishCallback : ()=&gt; skuid.$.unblockUI()
<jsitem location="inlinesnippet" name="loadNextAccount" cachelocation="false">skuid.$.blockUI();
    ()=&gt; skuid.$.unblockUI()
<actionsequences uniqueid="sk-3Yc7-103"/>
<styleitem type="background" bgtype="none"/>

Photo of Shmuel Kamensky

Shmuel Kamensky, Champion

  • 4,472 Points 4k badge 2x thumb
  • disappointed

Posted 4 days ago

  • 1
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,168 Points 20k badge 2x thumb
Shmuel.  Sorry for taking a few days to get back to you.  We were seeing this on an internal page and remembered this post.  We seem to have worked around the problem when we add the Id field to the OrderBy property for the model.  

Its reminscient of long standing problems we've seen with the standard set controller.  See Ben's discussion about that here: