Menachem;

This is an issue we see from time to time and seems to originate direclty from the Salesforce’s Standard Set Controller.  Its happening beneath anything that Skuid can control. 

We have usually been able to create a workaround though.  If you add a second field to your model “default order by” property it seems to reliably return the correct number of values. The code we put there was:  

We are exploring with Salesforce and others whether this issue is in their code or our implementation.   We hope to have it fixed soon, but in any case the workaround is available for you and should solve the immediate problems you were facing. 

Hey Rob,

Is there an update on this issue? 

Hello,

I’m seeing this behavior despite having several fields in the “Fields to order records by” field on the model.  If I put the max at 200, I get a resultset of 142.  If I put 80, and “load more”, it gives me 136 with no option to load the missing 6.

If I search, the missing records will come back in the result, but are otherwise lost to the user.

Any suggestions?

Thanks,

Paul

Paul,
I was not able to reproduce this problem in our latest version of Skuid. Can you tell us which you are on? Also, can you copy and paste your page XML here for us to investigate further?

Hi Paul, I wanted to see if you could grab the model’s SOQL query. That’s available by opening the browser’s developer console, and entering the command skuid.model.map(), then clicking on the model you’re troubleshooting. The SOQL statement should be within, and if you copy and paste it into Salesforce’s Developer Console and execute the same query, it might tell us something about why you’re seeing the behavior. 

It’s a lot of custom fields, some of which are a bit revealing in a way I’m not comfortable sharing here - can I email it to you?

Hi Mark, I have the same issue.

If I sort by a specific Field and Load More it only loads 9 more records(model loads the first 200 by default)  but there are 70 more which are supposed to be loaded…

If i remove that sort order or use a different field , it seems to work no problem.

I entered the SOQL Statement in the Dev Console and it returned all 270 records perfectly.

I am on a older version of Skuid (10.0.23) but never had this issue with any other table as far as i know…

Hi Dave. I’ve heard of some similar behavior in the past though I’ve not seen it happen myself. The recommendation in those cases was to sort by a field that’s always unique, like the record’s unique Id field. I think you can do this in addition to other ‘sort-by’ fields you need. Can you try this out and let me know if there’s a difference in behavior? I might also recommend getting a sandbox spun up on a newer release of Skuid to see if the behavior is different. 

adding the ID as 2nd sort seems to have fixed issue, thx

I’m having a similar issue here, in particular when using a specific table filter. I have a model loading 100 results, when I select a particular table filter and then select Load More, the load more button goes away and I still have my 100 results even though there should be 188 results returned.

If I remove the ORDER BY from my table, it doesn’t seem to help in this instance. I still get only 100 results and can’t load more for the rest.

It seems to only sometimes happen dependent on what filter conditions I specify on the table. It would be difficult for me to send over XML of this happening as it’s pretty deep in custom objects / our specific data to illuminate the bug happening.

SKUID v12.1.7, API v1

I’m seeing the same behavior - did you ever find a resolution to this?

Thanks!