Can't Use SQL View Without Granting SELECT Permission on Underlying Table

[TimNYC]

Good morning,

I'm trying to use a SQL view in my Power App. Everything was going fine as I built and tested the app, but prior to deployment I updated the user in my SQL database to only have the SELECT permission on the specific view used in the Power App. But now I get an error in my app that says the SELECT permission was denied on the table that view looks at. Using the view is an important security measure because it ensures that only the rows that I allow will be accessible via Power Apps. The SQL user I created can access the view just fine with any other application, for example, with SSMS, without having SELECT permission on the table. Is there a way to give Power Apps SELECT permission to views without giving it access to the view's tables?

I can't deploy my app if doing so means giving users access to all the data in the table. Even though I can restrict what the app sees with a view, the SQL connection is implicitly shared when I share the app and that would allow other users to build their own apps which can view all the data, right?

In this screenshot the object being referenced is not the view that I have connected to, but rather a table that the view uses.

Thank you,

Tim

[TimNYC · Accepted solution]

I figured out that this only happens to views that contain both tables and other views. Rewriting the view to include only tables solved the problem.