Table permissions for using GET with Web API

[Anonymous]

I'm using the newly implemented query data (GET) function in the Portal Web API. It works perfectly on tables with global access type table permissions, but when I try with the parent access type I get an error:

"code":"90040120","message":"You don’t have permission to read the X table.","type":"EntityPermissionReadIsMissing"

I verified that my user has access to this table through fetching the same data with FETCH XML and Liquid.
Is this a bug, or is there something I'm missing?

[chleverenz · Accepted solution]

Hi @Anonymous ,

did not use that feature yet but i could imagine, that you have to add the table holding the (parent)relationship to the web api enabled stuff as well. 

Not sure butthis is what i would do 🙂

Have fun,

  Christian

[Anonymous]

Hi,

thank you for the suggestion!

I had the webapi site setting enabled for the table I was requesting, but when I enabled it for the relationship-table as well it worked!

[Anonymous]

Sorry, I was a bit too quick to mark this as solved..

I've encountered a new error when using the request now:

{"error":{"code":"9004010D","message":"Common Data Service error occurred.","cdscode":"0x0","innererror":{"code":"0x0","message":"Could not find a property named 'access_controller_contact' on type 'Microsoft.Dynamics.CRM.access_controller'."}}}

I've tried enabling the webapi setting for this many-to-many relationship as well, without any luck. Any other suggestions? 

[chleverenz]

@Anonymous 

hm, when i see this kind of message, its usually true. Are you sure, that the right connecting entity was stated in the request? So, i am not that deep in that but is access_controller_contact really the name of a (connecting)table or is this a kind of message from the authorization controller trying to connect contact scoped tablepermissions to something?

I sometimes had also issues, when too many tablepermissions were applied to a table, becausae it exceeded somehow a limit of linked-entities as the fetch is extended by applying entitytable permissions.

So, may be try to reduce the tablepermissions just for a test when there are many tablepermissions or the requested tables.

Have fun,

  Christian