Apply Developer Tools
The toolchain
Development happens in Visual Studio with the Dynamics 365 Finance and Operations tools extension. Application Explorer is a read/write view of the entire AOT; Solution Explorer shows only your project. The Dynamics 365 menu exposes Model management (create, import and export models), Build models, Synchronize database, and best-practice options.
The daily loop
Edit elements, build the model, run the best-practice check, synchronize the local database (development VMs only, never production), then run or debug against the local site. Debugging a cloud-hosted environment requires enabling debugging in LCS and attaching Visual Studio with environment credentials.
Source control and pipelines
Connect the workspace to Azure DevOps using TFVC or Git through Source Control Explorer, and check in small changes with meaningful comments. A build pipeline compiles, runs best-practice checks and tests, and produces the deployable package that LCS pushes to downstream environments.
Traps
Confusing Synchronize database with a deployment: it is a schema sync on a dev box and rebuilds tables. Confusing warnings with errors in the best-practice results: error-level deviations fail the build and must be fixed, warnings are review items. Assuming Task recorder output is documentation only: it can generate a business process model and, with the BPM tool, a deliverable. Rule of thumb: build, run best-practice checks, synchronize, and test locally before creating a package; the package is the only artifact that travels.