CascadeFields.Configurator
1.2026.1.173
Requires NuGet 5.10.0 or higher.
dotnet add package CascadeFields.Configurator --version 1.2026.1.173
NuGet\Install-Package CascadeFields.Configurator -Version 1.2026.1.173
<PackageReference Include="CascadeFields.Configurator" Version="1.2026.1.173" />
<PackageVersion Include="CascadeFields.Configurator" Version="1.2026.1.173" />
<PackageReference Include="CascadeFields.Configurator" />
paket add CascadeFields.Configurator --version 1.2026.1.173
#r "nuget: CascadeFields.Configurator, 1.2026.1.173"
#:package CascadeFields.Configurator@1.2026.1.173
#addin nuget:?package=CascadeFields.Configurator&version=1.2026.1.173
#tool nuget:?package=CascadeFields.Configurator&version=1.2026.1.173
CascadeFields for Microsoft Dataverse
<img width="1248" alt="CascadeFields configurator hero" src="https://github.com/user-attachments/assets/d1d0aa60-c8b5-4585-9d45-7dff22d8587a" />
CascadeFields is a Dataverse plug-in plus an XrmToolBox Configurator that helps keep related records in sync by cascading field values from parent records to their related child records.
<img width="1349" alt="CascadeFields configurator screenshot" src="https://github.com/user-attachments/assets/6c0cd72e-80f4-4b9d-833d-629f343cbd55" />
Why CascadeFields?
Keeping related records consistent in Dataverse often means manual updates, complex Power Automate flows, or custom plug-in development. CascadeFields is intended to give admins and teams a fast, repeatable way to keep child records aligned with parent data while remaining solution-aware and easy to manage.
Doesn't this result in data duplication? Sure, yes. But there are cases where duplicating the data makes it easier for users to search/filter within Dataverse. A simplified example is where you have the hierarchy of Account-Contact records. If a record is attached to the contact record via a lookup it is readily visible in the child's related records, but if you go to the Account record (the parent of the contact) this child-of-a-child record is not in a related view. Now consider if the records are arranged in a multi-level hierarchy: keeping a link to the parent records on the ultimate child record goes a long way toward making the records easily discoverable by an end-user. It is an option for you when you want to add these extra shortcuts or relationships just to make the app easier to use through the front-end. If it helps, great! If you want to solve it another way, also great! 😃
What it does
- Cascades changes from a parent record to matching child records (typically async for performance)
- Populates mapped fields when a child record is created and linked to a parent
- Updates mapped fields when a child record is re-linked to a different parent
- Supports trigger fields and optional filters to control when and what is updated
Components
- CascadeFields Configurator: XrmToolBox UI used to build, validate, and publish configurations
- CascadeFields Plugin: Dataverse plug-in that executes the configured cascade behavior
Key features
- No-code configuration from within XrmToolBox
- Trigger fields (control which parent changes cause cascades)
- Optional filter criteria (control which child rows are updated)
- Supports parent update cascades and child create/relink scenarios
- Designed for performance (asynchronous parent updates where appropriate)
- Diagnostics via Dataverse plug-in trace logs (when enabled at the environment level)
Docs Index
- Admin usage (XrmToolBox): QUICKSTART.md
- Configuration JSON reference: CONFIGURATION.md
- Build, packaging, manual registration, contributing: PRODEV.md
- Examples: Examples
License
Licensed under the MIT License.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET Framework | net462 is compatible. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
.NETFramework 4.6.2
- XrmToolBoxPackage (>= 1.2025.10.74)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Review CHANGELOG or git history for details.