Can Skuid call UserRecordAccess now (based on the recent release)?

edited June 25, 2020 in Questions
The SFDC object UserRecordAccess does not have an ID column, which has made using it in a Skuid model a non-started. The latest release notes say:


 - Support for objects, fields, and metadata available in Salesforce API version 33 (Spring 15)

Does this mean that UserRecordAccess can be used in a model?



  • edited April 30, 2015
    And - sorry for the typos! Trying to post whilst on a train :-( .
  • Rob HatchRob Hatch 💎💎💎
    edited September 1, 2016
    No worries.  I'm tying this in a concert hall, waiting for a son's spring band show... 

    We have not yet upgraded Skuid to use API 33. We will probably do so in our next release.  But at that point it is likely that UserRecordAccess will be more accessible. 
  • edited April 30, 2015
    Rob - Thanks!
  • edited May 2, 2015
    @Rob Just to be clear :-) , even though the Superbank - Patch 7 release notes say "Support for objects, fields, and metadata available in Salesforce API version 33 (Spring 15)", this support does not include Skuid models accessing the UserRecordAccess object - right? 
  • Rob HatchRob Hatch 💎💎💎
    edited June 25, 2020
    So,  we are on API 33, but It doesn't look like Salesforce has completely made the UserRecordAccess object look like a normal object.  Though there is now an ID field on the object,  Salesforce will still not let us query it.  Sorry about this. 
  • Pat VachonPat Vachon 💎💎💎
    edited June 2, 2016
    Is this still the case?
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!