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

  • 1
  • Question
  • Updated 2 years ago
  • Answered
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:

ENHANCEMENTS: 

 - 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?

Thanks!
Photo of Andy Forbes

Andy Forbes

  • 322 Points 250 badge 2x thumb

Posted 4 years ago

  • 1
Photo of Andy Forbes

Andy Forbes

  • 322 Points 250 badge 2x thumb
And - sorry for the typos! Trying to post whilst on a train :-( .
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
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. 
Photo of Andy Forbes

Andy Forbes

  • 322 Points 250 badge 2x thumb
Rob - Thanks!
Photo of Andy Forbes

Andy Forbes

  • 322 Points 250 badge 2x thumb
@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? 
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
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. 
Photo of mB Pat Vachon

mB Pat Vachon, Champion

  • 42,714 Points 20k badge 2x thumb
Is this still the case?