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.
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.
docs: update migration guide links and clarify command references
Add migration guides for Daxif and PACX to Flowline documentation - Created a comprehensive guide for migrating from Daxif to Flowline, detailing command mappings, migration phases, and step-by-step instructions for plugin registration, web resource management, and solution operations. - Added a migration guide for transitioning from PACX to Flowline, highlighting command equivalents, two-phase migration strategy, and project setup differences.