Skip to content

Dynamic Logic Plus Example

Overview

Dynamic Logic Plus Example

This example uses the Payment entity. The screenshot shows a setup with these links/fields:

  • Orders
  • Payment Attempts
  • Account
  • Contact
  • Amount

Cascade Update Triggers

We have a formula on Orders that calculates paid amount.

  • In Triggering Fields, select Amount.
  • In Link, select Orders.

Now, when Amount changes on a Payment, linked Orders records are re-saved so formulas can be recalculated.

Cascade Remove

When a Payment is deleted, related Payment Attempts should be deleted automatically.

Prevent deleting a Payment if it has related Orders records.

Users must remove linked Orders first, which protects data integrity.

Make Account and Contact dependent:

  • When Contact is selected, Account can be auto-filled.
  • When Account is selected, Contact autocomplete/modal selection is filtered by that Account.
  • Orders can be configured to depend on both Account and Contact in the same way.

Note

Do not place the same link in both Cascade Remove and Links Must Be Empty Before Remove.