Approval Dashboard
The Approval Dashboard is a Power App developed by 9altitudes that seamlessly integrates with the Process Management module as part of the Raptor D365 F&O integration.
About Approval Dashboard
The Approval Dashboard app enables users to manage approval workflows outside the ERP system while leveraging the Raptor Document Warehouse to visualize the documents requiring approval. The Power App is provided as a Kickstart package with essential approval functionality. It is delivered as an Unmanaged solution, allowing low-code developers to customize and extend the app to meet your organization’s specific needs.
Accessing the Power App
Depending on your setup, you can open the Power App either through Power Apps (Dataverse) or Microsoft Teams (Dataverse for Teams).
1. Access via Power Apps (Dataverse license)
Open your browser and go to https://make.powerapps.com.
Sign in with your Microsoft 365 account.
In the left-hand menu, select Apps.
Find the app you want to open — for example, Approval Dashboard.
Click the app name to launch it.
(Optional) Pin the app to your favorites for quicker access next time.
2. Access via Microsoft Teams (Dataverse for Teams)
Open Microsoft Teams.
Go to the team or channel where the app has been published.
In the tab bar at the top, look for the Power App tab (e.g., Approval Dashboard).
Click the tab to open the app directly within Teams.
(Optional) If you don’t see the tab, click the Apps icon in the left sidebar and search for the app name to add it manually.
Sharing the Power App with Other Users
You can easily share the Power App with colleagues so they can also access and use it. The sharing method depends on where the app is hosted.
1. Sharing from Power Apps (Dataverse license)
Go to https://make.powerapps.com and sign in.
In the left-hand menu, select Apps.
Find the app you want to share (for example, Approval Dashboard).
Click the three dots (…) next to the app name and choose Share.
In the sharing panel:
Enter the names or email addresses of the users or security groups you want to share the app with.
Choose the appropriate permissions:
Can use – allows users to run the app.
Can edit – allows users to modify the app (for makers or low-code developers).
Click Share to confirm.
The users will now see the app in their Power Apps environment.
2. Sharing from Microsoft Teams (Dataverse for Teams)
Open Microsoft Teams.
Navigate to the team where the app is published.
Go to the Power Apps tab (e.g., Approval Dashboard).
Click the More options (⋯) icon next to the tab name, and select Manage access (or App details depending on your Teams version).
Add additional team members if needed — everyone who is part of that Team automatically gets access to the app.
If you need to share the app with users outside the Team, you can either:
Add them as members of the Team, or
Publish the app in another Team or environment.
Adding an Admin User
The admin user has an additional privilege: they can assign other users as approvers on behalf of someone else. When the admin user performs this action, a user will then be able to view the invoices of another user.
To add an admin user, follow these steps:
In Power Automate, open the appropriate Solution.
Click on Tables.
Search for the table AdminUser.
Add the email address of the person who should be assigned as an admin.
Act on Behalf Of
An admin user has access to an additional button in the app: Settings. In this screen, the admin can specify on whose behalf another user is allowed to perform approvals.
Click on the desired user.
A text field will appear at the bottom right of the screen.
Enter the email address of the person on whose behalf approvals should be made.
Click Add to confirm.
Troubleshooting
If an invoice does not appear in the Approval Dashboard, or if an approved invoice is not correctly reflected in Finance & Operations (F&O), there may be an issue with one of the Power Automate flows.
In such cases, it is recommended to open the Cloud Flows listed below to identify the source of the problem. Here you can view all available flows connected to the app. Each flow has its own specific purpose and function. Below is an example of the screen that appears when you click “Cloud Flows.” If you then click on a flow, you can view the run history of that specific flow.
Below you can see the history of the flow that was executed to notify F&O that an invoice has been approved.
On the left side, you can see when the flow was run. Clicking on this entry allows you to view detailed information about what succeeded and what failed.
On the right side, you can see which flows ran successfully and which encountered errors.
Maintaining Connection References in the Solution
Connection references define which services your app and flows use. Keeping them up to date ensures that your Dataverse, F&O, email, and Office 365 integrations continue to work correctly.
1. Open the Solution
Go to https://make.powerapps.com and sign in.
In the left-hand menu, select Solutions.
Open the Solution containing your app and flows.
2. Locate Connection References
Inside the Solution, click Connection References in the left-hand menu.
You will see all existing connections, such as:
Dataverse – for accessing tables and data.
Finance & Operations (F&O) – for ERP integration.
Mail (Office 365 Outlook) – for sending approval notifications.
Office 365 Users / Other Office services – for user profiles or additional actions.
3. Update or Reconnect a Connection
Click on the connection reference you want to maintain.
If the connection is broken, expired, or requires a different user, click Edit or Reconnect.
Sign in with the appropriate credentials for that service.
Save your changes.
4. Verify Connections in Flows and Apps
Open each flow in the Solution.
Check that the connection references are correctly applied in all actions.
Do the same for the Power App, ensuring that all data sources point to the correct connection references.
5. Best Practices
Use service accounts for connections that require shared access, rather than individual user accounts.
Regularly review connection references to prevent failures due to expired credentials.
Keep documentation of which account is used for each connection.
Last updated