Created with AI.
Building on Dataverse gives the app access control and traceability without you having to build them yourself. Here are the steps—and the pitfall that can cause users to see more than they should.
If you have test and production environments, check which one you are in before you start building. Building an app using test data that will need to be moved later creates unnecessary extra work.
Include what the app uses, not everything that's available. Fewer tables make the app faster and easier to maintain.
The user sees only what the security role permits in Dataverse—nothing more. That is an advantage, but it also means that the app may appear empty to a colleague even if it works for you.
This is the most important step. As the person building the app, you usually have elevated permissions. Ask a regular user to open the app, or test it using an account with the same role as the actual users.
If the app will be used outdoors, clarify what happens when there is no coverage. It is better to know now than to hear it from a frustrated user.
Ask a question or share what helped you.

Published 1/25/2024
BUA lends out sports and outdoor equipment through local branches and has experienced significant growth. They have therefore explored opportunities to create a system that ensures continued operations as they expand further.
Read more
Published 2/12/2025
ProsessPilotene has developed a completely new solution for payroll deductions. TrekkSenter makes it easy for both trade unions and payroll departments to process deduction lists.
Read moreDo you have a question or experience to share?
Be the first to contribute.