I would like to maintain views in the SF which should be part of a different database schema, so not dbo.
Use case is a set of views which will be authorized for a group of users (via Excel link) of reporting system (e.g. PowerBI) to query on.
Assigning the rights is much easier if a specific schema can be assigned to create the views.
Also it will be clear what the purpose is of a certain set of views.
I’ve always wondered (alas though, I’ve never asked) why schema’s are not used within the platform.
Anyone here that can elaborate on why schema’s are not (ab)used within the platform (i.e every module its own schema)?
Hi all,
Our view is that the database should not be directly accessible by the user. All authorization, permissions and authorization scopes are based around RBAC, the roles defined in the application.
Ideally, this is then guarded by the API. For now, it is also still possible to effectuate these roles on the database.
Schema-based access isn’t something the Thinkwise platform supports, and not all relational database management systems support schemas in the same way.
An approach would be to define a role for the views to be used for PowerBI which has the same scope as the mentioned schema.
We’ll close this idea as it does not align with our current vision of the platform and how it interacts with the databases.
As such, we don't see it being implemented in the foreseeable future.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.