The Dynamics 365 FastTrack team uses this repository to share Dynamics 365 F&O and Commerce best implementation guidelines. These may be documentation, extension code, business practices etc.
Outline the file contents of the repository. It helps users navigate the codebase, build configuration and any related assets.
| File/folder | Description |
|---|---|
Finance |
Dymamics 365 Finance guides |
Commerce |
Dymamics 365 Commerce guides |
Analytics |
Dymamics 365 Analytics guides |
SQL Maintenance |
Indexes & statistics maintenance script |
Dual-write |
Dymamics 365 Dual-write guides |
SCM |
Tools for SCM and WHS solutions |
ScheduleAPI |
Project Operations - Schedule API example |
Cloud security |
Dynamics 365 Cloud security guides |
Integration |
Dynamics 365 integration samples |
.gitignore |
Define what to ignore at commit time. |
CHANGELOG.md |
List of changes to the sample. |
CONTRIBUTING.md |
Guidelines for contributing to the sample. |
README.md |
This README file. |
LICENSE |
The license for the sample. |
- POS UI Negative inventory check/prevention (CRT extension)
- Ecommerce load test sample
- Dynamics 365 Commerce storefront E2E functional test sample
- Small Parcel Shipping Tools A sample TMS DLL is included for testing SPS scenarios without a live connection to a carrier.
- Schedule API PO_ImportFile.ps1.
- Integration Dynamics 365 integration samples.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.