8

Can someone help me understand why this query is returning 1 less record than expected when a Date custom field (Due_Date__c) is included in the SELECT clause? As you can see in the screenshot, it's returning 180 of 181 records. It is not sending a nextRecordsUrl for a queryMore, and with only 181 records, there's not really a reason it would. It's just returning one less record than it says it will.

SELECT Id, Due_Date__c FROM Case WHERE MHHE_Mobile_Sync_Flag__c = trueenter image description here

If I remove the Due_Date__c field, I get 181 of 181 returned, as expected:

enter image description here

Is there any logical reason this would happen?

Improve this question
2
  • is the output above from workbench? what happens if you execute the query in developer console?
    – cropredy
    Jul 3, 2014 at 22:10
  • The output shown here is from Workbench for illustration, yes. The issue I'm having is in a custom iOS/Obj-C app, and I get the same result in SoqlXplorer. The user in question doesn't have access to the developer console, and the query with an Admin account seems to just be timing out in the dev console.
    – Tom Gersic
    Jul 7, 2014 at 14:41

1 Answer 1

Reset to default
1

You could try comparing the Ids from both results to find the one record that is not coming back when you get 180 of 181 records returned.

Once you know the record Id, try doing a specific query for just that record. E.g.

SELECT Id, Due_Date__c FROM Case WHERE Id = 'a0e000000000001'

You can also check how this one record appears for the user in question when viewed directly in the Web UI.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .