Difference between revisions of "How to document your solutions"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Best Practice and naming conventions - Best to figure this out before you start with your project in order to establish a common way of working. | * Best Practice and naming conventions - Best to figure this out before you start with your project in order to establish a common way of working. | ||
| − | * Entity Relationship Diagram (ERD) visualizing the essential OOTB Tables that make up your solution as well as all custom tables and the relationships in between | + | * Entity Relationship Diagram (ERD) visualizing the essential OOTB Tables that make up your solution as well as all custom tables and the relationships in between. |
| − | * Environments that are used and settings specific for each environment (that are not deployed through solutions, e.g. search settings or configuration data) | + | * Environments that are used and settings specific for each environment (that are not deployed through solutions, e.g. search settings or configuration data). |
| − | * ALM and deploy procedure - info about pipelines, the setup and who is responsible for deploys | + | * ALM and deploy procedure - info about pipelines, the setup and who is responsible for deploys. |
* Solution Components - Description of Tables, relationships in between, Business Rules, Business Process Flows (BPF), Cloud flows, Plugins etc. | * Solution Components - Description of Tables, relationships in between, Business Rules, Business Process Flows (BPF), Cloud flows, Plugins etc. | ||
| − | * Integrations - What integrations there are, diagram illustrating integration flows, integration techniques, mappings | + | * Integrations - What integrations there are, diagram illustrating integration flows, integration techniques, mappings. |
If Azure DevOps is used, a Project Wiki can be used to store information about environments, settings and pipelines. If Microsoft Teams is used, a OneNote can be used as wiki. | If Azure DevOps is used, a Project Wiki can be used to store information about environments, settings and pipelines. If Microsoft Teams is used, a OneNote can be used as wiki. | ||
Revision as of 12:43, 20 December 2021
This page gathers information about tips and tricks (tools) you can use when documenting your Power Platform solutions.
General
So you have created a Power Platform solution and users are now using it in a production environment. In order to be able to maintain the solution over time it is important to establish and maintain documentation as well.
Examples of what documentation that is useful to have:
- Best Practice and naming conventions - Best to figure this out before you start with your project in order to establish a common way of working.
- Entity Relationship Diagram (ERD) visualizing the essential OOTB Tables that make up your solution as well as all custom tables and the relationships in between.
- Environments that are used and settings specific for each environment (that are not deployed through solutions, e.g. search settings or configuration data).
- ALM and deploy procedure - info about pipelines, the setup and who is responsible for deploys.
- Solution Components - Description of Tables, relationships in between, Business Rules, Business Process Flows (BPF), Cloud flows, Plugins etc.
- Integrations - What integrations there are, diagram illustrating integration flows, integration techniques, mappings.
If Azure DevOps is used, a Project Wiki can be used to store information about environments, settings and pipelines. If Microsoft Teams is used, a OneNote can be used as wiki.