Structure of projects

The folder structure of a Dataverse project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure. No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.

A possible structure could look like the following: root ├── Development │ ├── Azure │ ├── Back-end │ │ ├── Applications │ │ ├── Plugins │ │ ├── Shared │ │ ├── Workflows │ ├── Front-end │ │ ├── PCF │ │ ├── ts │ │ │ ├── src │ │ │ │ ├── code │ │ │ │ │ ├── utils │ │ │ │ │ ├── tables │ │ │ │ │ ├── ribbon │ │ │ ├── test │ │ ├── Webresources │ │ │ ├── HTML │ │ │ ├── CSS │ │ │ ├── images │ │ │ ├── js │ ├── spkl ├── PowerPlatform │ ├── CanvasApps │ ├── Config │ │ ├── Schema │ │ ├── Data │ ├── Solutions │ ├── (Tools) ├── Pipelines

Community Content

• Folder structure of a Dataverse project by Benedikt Bergmann