Skip to main content

When a model is marked to be processed client side, if no value is specified for “Max # of records (Limit)” a remoting exception is encountered.


Steps to reproduce:


  1. Create blank page

  2. Add “Account” model pointing to Account, add Name field and leave all other defaults

  3. Preview page - Expected = Actual = Page loads as expected with no errors

  4. Change “Account” model to “Process client side”

  5. Preview page - Expected = Actual = Page loads as expected with no errors

  6. Change “Account” model removing the value for Max # of records

  7. Preview page

Expected - Page loads without error

Actual - Page encounters remoting exception



Sample Page XML


<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" showheader="true">   <models>
<model id="Account" limit="" query="true" createrowifnonefound="false" adapter="" type="" sobject="Account" doclone="" processonclient="true">
<fields>
<field id="Name"/>
</fields>
<conditions/>
<actions/>
</model>
</models>
<components/>
<resources>
<labels/>
<javascript/>
<css/>
</resources>
<styles>
<styleitem type="background" bgtype="none"/>
</styles>
</skuidpage>

Sad face indeed. Client side processing is so new - I’m sure there are going to be lots of corners that need to be polished. 


Thanks for pointing this out Barry! I’ve fixed this, and it will be out with the next patch.


You’re on a roll Andrew, thanks again for all your help on this and the other issues, greatly appreciated!


Tested and confirmed as resolved in Skuid 7.16.  Thank you!


Reply