Taxi dispatch style dashboard in PowerApps
Budget: £750 – £1,500 GBP
I work for an outdoor activities and training organisation, we are using a spreadsheet to track the specifics of each group of customers EG locations activities staff working with the group individuals within the group. I have got a good way to to creating a powerapp to replace this while tying in our CRM and incident and note reporting systems, however other projects are pulling me away from this. I I'm looking for a power platform professional who can finish what I have started.
Information I intend to attempt to draw from existing data sources as much as possible, using dataverse tables to patch gaps where existing data sources I'm missing.
We are using Salesforce as a CRM and managing staffing in Shifts for Teams. You may well be using the Dynamics fixed asset module in order to control r equipments used on the sessions however if not a custom data source within dataverse may be required, which would need to tie in with a system of recording defects and repair schedules. The the equipments maintenance system will not be part of this project, just the datasource designed to work with one.
In general, it is important that this system is designed to be extended, and with a possible change of Datasources in mind. I know it's not exactly a thing in PowerApps, but something akin to the OOP, "getters and setters" approach at the point of interacting with the datasource would be preferred. I also prefer parameters to be dynamic where possible, so text "size" parameter, to refer to a value that is editable in a settings interface within the app.
Information I intend to attempt to draw from existing data sources as much as possible, using dataverse tables to patch gaps where existing data sources I'm missing.
We are using Salesforce as a CRM and managing staffing in Shifts for Teams. You may well be using the Dynamics fixed asset module in order to control r equipments used on the sessions however if not a custom data source within dataverse may be required, which would need to tie in with a system of recording defects and repair schedules. The the equipments maintenance system will not be part of this project, just the datasource designed to work with one.
In general, it is important that this system is designed to be extended, and with a possible change of Datasources in mind. I know it's not exactly a thing in PowerApps, but something akin to the OOP, "getters and setters" approach at the point of interacting with the datasource would be preferred. I also prefer parameters to be dynamic where possible, so text "size" parameter, to refer to a value that is editable in a settings interface within the app.