We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
docs: update project structure references to use Solution/ instead of Package/ and clarify project file naming conventions
Update wiki for single-solution root-level layout (Flowline plan U7) Flowline moved from a solutions/<Name>/-wrapped, multi-solution-array project model to exactly one Dataverse solution per project root. Updates across 10 pages: folder-structure diagrams and path examples flattened to root level; deploy's --solution flag and sync/drift's positional [solution] argument removed from docs (both CLI surfaces were removed entirely); push/generate's positional argument reworded to describe mismatch-validation against the single configured solution rather than selection among several; deploy's dirty-check and artifact-cache docs updated to name the narrower deployment-input scope (Package/, Plugins/Plugins.csproj, WebResources/WebResources.csproj) instead of the whole solution folder; AGENTS.md template reproduction updated to match its rewritten source; migration guides' target paths flattened; Getting-Started adds a pointer to the main repo's manual cutover steps for projects still on the old layout.
Add migration guides for Daxif, PACX, and ALM Accelerator; introduce planned features - Created migration guide from Daxif detailing equivalent commands and migration steps. - Added migration guide from PACX outlining command mappings and two-phase migration strategy. - Developed migration guide from ALM Accelerator, emphasizing deployment model changes and mapping to Flowline commands. - Introduced a new document for planned features, including post-deploy state reconciliation and CLI setup enhancements.