Extend Custom Component Event data with (basic) authorizations

​@Freddy We are not inclined to add a lot of information to the event data messages provided by Universal to Custom Components, because we want to keep these lightweight.

What would be your use-case if this information would be provided in the event message? Would you be satisfied if you only know whether a user has read access vs write access for example?

I do understand. And maybe the event message is not the correct place, as you would typically want to know this for all entities. Is there a way via the oData way to see this? Now it just returns what is filled or what is autorized with no automated way to tell why data is absent.  

It would though be helpful if the event data aside the entity would give the PK of that entity. I'm building a document center, as there is no multi-upload in TW, and to not make a custom component for every entity it would be great to get besides the entity also the PK of that entity.. Should be enough to make a single component that I can load on al main entities that can hold documents. 

​@Freddy You could try calling the odata endpoints for the i_ui_tab(e.g. http://localhost/indicium/iam/iam/i_ui_tab) and i_ui_col(e.g. http://localhost/indicium/iam/iam/i_ui_col) views. These are endpoints used by universal that contain the model information about whether a table / column is visible or can be edited. For example this is part of the return of the i_ui_tab:

You can then filter them using ODATA filters to only retrieve the information for the subject used by the custom component. For examples on how to do that, you can look at the requests send by Universal itself.

I agree with the second part that adding the primary key information to the message could be useful. For now I think you are also able to retrieve that information by calling the i_ui_col endpoint as it is is a parameter for a column field: