Configuring Rent Table Inheritance and Validation Settings

    Overview

    AscendixRE 1.43 adds a set of Rent Table settings covering three areas: carrying a Deal's Rent Table onto its Lease at close, a non-blocking review notice for incomplete or inconsistent Rent Table periods, and a relaxed field-level requirement on Rate and Rent Per Month. All of these are controlled through AutomationSetting__mdt records in the AscendixRE Admin Console.

    Admin Responsibilities:

    • Decide whether Rent Table inheritance from Deal to Lease should be turned on
    • Review the default-active Rent Table validations and adjust if needed
    • Update any customized Rent Table Period page layouts

    Prerequisites

    • Permission Set Required: AscendixREAdmin
    • Familiarity with the AscendixRE Admin Console's Business Logic tab (Automation section)

    Configuration

    Step 1: Turn on Rent Table inheritance from Deal to Lease (optional)

    AUTOLeaseRentTableFromDeal ships inactive. When active, closing a Tenant Representation or Landlord Representation Deal carries the Deal's Rent Table onto the Lease created at close — including when Size, Lease Rate per SF, Lease Commencement, or Lease Expiration are edited on the Deal Close page itself. A Lease that already has its own Rent Table is never overwritten.

    1. Open the AscendixRE Admin Console.
    2. Go to Business Logic → Automation.
    3. Find AUTOLeaseRentTableFromDeal and set Is Active to true.

    Note: This only affects Leases created going forward — it does not change any Lease Rent Table that already exists.

    Step 2: Review the Rent Table review-notice settings

    VALDealRentTableReview and VALLeaseRentTableReview ship active by default. When active, AscendixRE shows a non-blocking notice on the Deal or Lease if Rent Table periods have a gap, overlap, or blank rent (a zero-rent free-rent period is not flagged). This never blocks saving a period, the Deal, or Deal close.

    1. In Business Logic → Automation, find VALDealRentTableReview / VALLeaseRentTableReview.
    2. Disable, or scope by record type, if this notice doesn't fit your process.

    Step 3: Review the Rate / Rent Per Month requirement

    VALDealPeriodRentRequired and VALLeasePeriodRentRequired work together with the packaged validation rules PreventBlankRateAndRentPerMonth (on both DealPeriod__c and LeasePeriod__c) to require that at least one of Rate or Rent Per Month is filled in on a period — replacing the previous page-layout-level "Required" checkbox on both fields.

    To bypass this validation for a specific bulk-load or integration scenario, use the new DealPeriodValidation__c / LeasePeriodValidation__c fields on BypassValidationRules__c, consistent with the standard trigger-framework bypass pattern.

    Step 4: Update customized Rent Table Period layouts (optional)

    If you upgraded from R 1.40, R 1.41, or R 1.42, Rate and Rent Per Month were required at the field level in those releases. If you customized the Deal Period Layout or Lease Period Layout (or any clone of them), remove the Required checkbox from both fields — the package no longer marks them required on packaged layouts.

    1. Go to Setup → Object Manager → Rent Table Period (DealPeriod__c) → Page Layouts → Deal Period Layout.
    2. Double-click Rate, uncheck Required, click OK. Repeat for Rent Per Month. Click Save.
    3. Repeat for Rent Table Period (LeasePeriod__c) → Lease Period Layout, and for any other cloned Rent Table Period layout.

    Note: Orgs upgrading from R 1.39 or earlier are not affected — the fields weren't required at the layout level before R 1.40.


    Troubleshooting

    1. A Lease isn't inheriting its Deal's Rent Table at close
      1. Confirm AUTOLeaseRentTableFromDeal is active.
      2. Confirm the Deal is Tenant Representation or Landlord Representation.
      3. Confirm the Lease didn't already have its own Rent Table before close.
    2. The review notice doesn't appear for a Rent Table with a gap
      1. Confirm VALDealRentTableReview / VALLeaseRentTableReview is active and not scoped away from that record type.

    If the issue persists, contact your Ascendix representative.