Is it possible to prevent general users from having access to a data connection while allowing the users to read?
Sounds like a contradiction, I know. I have already achieved preventing access to the data connections using the DataConnection security rule - limiting permission to the built in admins only. Works great. General users cannot then see the data connections.
But I am now adding the 'Reload' button extension and I've just figured out that for a general user to use this function they must have read against the connection used by the app. Giving them these permissions then exposes the connection to the user to use in their own app which we cannot permit.
Does anyone know a way to permit data connection access for the reload function only - ie, not then be able to use or see the data connection directly? Note that there are some data connections that I do want to make available, so a blanket workspace ban won't work.
We use this solution. They have to be able to read the data connection to use the reload button because it reloads it client-side, not server side. So you have to choose - either they can see the data connections and reload, or not reload. The last option would be to prevent them from seeing the data load editor with security rules.
I don't have access to a server currently to try this with but you should be able to create a custom property on the extension that you could use to do this in a security rule. From what I understand though you don't want users to have read permission on the data connection at all and they would need that with the extension, so this still doesn't help. Still this comment might help someone down the track.