So since the canvas app has no managed property, how do you secure it in your managed solution? When distributing, how do you make sure your clients don't change it or simply export it for other purposes?
@natrob They said I had identified an issue as it should be non-editable by design. They logged it to be fixed in a release soon.
That's great news @AmirBakht , thanks for replying. Did they give an estimated time range or did they just say soon?
Sadly, there is currently no way to secure a Canvas app that has been installed via managed solution into a Dataverse/CDS environment. The person who installs the solution file becomes "owner" of the canvas app. They, and anyone they assign as co-owner, are able to open and edit it all they want. I just did this last week in testing an app so I know it is correct as of this writing.
When developed in one region (e.g. US) and opened by a customer in another (e.g. Canada, Australia), there is a risk the app will break based on different canvas app designer versions being used in the regions. This can turn into a huge tech support time waste for ISVs or corp dev teams.
(Suggestion: Turn off auto-save in make.powerapps.com)
-Art
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 |