Skip to main content
Sign in

Release Notes 3.30.2026

🛠 Enhancements

Trakref Integration – Manual Sync

image-20260323-224225.png
image-20260323-224254.png

Providers can now manually trigger the Trakref refrigerant compliance integration directly from a work order — giving teams more control over when and how compliance data is synced.

What's New:

  • A new Sync Trakref button has been added to the work order screen. It is only visible on HVAC/R work orders where the Trakref integration is enabled.

  • Clicking the button opens a modal pre-populated with the work order number, location, and vendor. The provider then selects the asset, service event type, and assignment before submitting.

  • Assets that are not yet synced to Trakref are clearly labeled "Not in Trakref." Vendors can click "Report Asset as Missing" to log the gap directly on the work order, so it can be addressed.

  • On successful submission, the modal closes automatically and a confirmation toast notification appears.

  • Required fields are validated before submission — users will be prompted if anything is missing.

‌

Asset & Invoice Mapping Enhancements

Fexa now gives you greater visibility and control over how invoice spend is tracked against your assets — making it easier to understand the true cost of maintaining your facilities over time.

What's New:

  • Asset allocation can now be triggered at invoice submission in addition to approval, giving accounting teams more flexibility in when assets are mapped to invoices.

  • When both automatic and manual allocation are enabled, Fexa handles simple cases automatically — mapping assets when there's a clear 1:1 match — and prompts you to confirm when multiple assets are involved.

  • Assets identified on invoice line items are now automatically associated with the parent work order, keeping your asset history complete even when assets weren't added at the time the work order was created.

  • Invoice spend is now attributed at the line-item level, giving you a more accurate picture of what's been spent on each individual asset over time.

  • A data migration has been applied to backfill asset associations on historical work orders, so your existing spend data is as complete and accurate as possible going forward.

    • NOTE: Automatic mapping is default if 1:1. Site setting allows for manual asset mapping. This is where the pop-up appears to allocate line items for the asset, so that spend gets allocated appropriately.

 

Work Order Summary Email – Problem Full Path

Previously, the Work Order summary email sent to vendors only showed the leaf-level problem category (e.g., "Not Working"), without any context about where that problem sat in the hierarchy. This made it harder for vendors to understand the full scope of the work before arriving on site.

What's Changed:

  • The Work Order summary email can now display the full problem path (e.g., "HVAC | Heater | Not Working"), giving vendors clearer context about the work being requested.

  • The full problem path is also now available as a column in Reports (Problem Full Path / With All Ancestors).

🐛 Bug Fixes

Toggle Custom Fields Incorrectly Set to True via "Don't Save" Modal

Resolved an issue where toggle custom fields were being unintentionally saved as true after a user selected "Don't Save" in the Unsaved Changes modal.

What's Fixed:

  • Previously, triggering the "Unsaved Changes" modal (e.g., by updating a work order status) and selecting "Don't Save" would cause all toggle custom fields to be set to true — even if the user had never interacted with them.

  • If the user then made another change and saved, those true values were incorrectly persisted, potentially triggering unintended workflows, automations, or notifications.

  • Toggle custom fields now only update when explicitly modified by the user.

 

GL Code Logic Ignoring Empty String Values

When duplicating a subcontractor invoice where the GL code had been set to an empty string (e.g., a single space), the GL mapping logic was being skipped entirely. This meant that GL codes were not being applied to duplicated invoices even when a matching GL Mapping rule existed.

What's Fixed:

  • Empty string GL codes are now treated the same as a blank value, ensuring GL mapping rules are evaluated and applied correctly when duplicating invoices.

 

Service Area Service Provider Report Column Typed as Number

The "Service Area Service Provider" column in Reports was incorrectly configured as a number field instead of a text field. This prevented users from adding it as a filter when building reports with Service Areas as the data source — the filter would appear but no value could be entered.

What's Fixed:

  • The "Service Area Service Provider" column is now correctly typed as a text field and can be used as a filter in reports.

 

Invoice NTE Status Showing Incorrectly for Multi-Currency Facilities

For facilities using a different currency than the site's base currency, the invoice widget (the green/red NTE indicator) and the backend NTE billing requirement check were using different rounding methods. This caused invoices to appear as under NTE in the UI while the system simultaneously flagged them as over NTE — creating a confusing and unreliable experience.

What's Fixed:

  • The backend NTE calculation now uses the same line-item level rounding as the frontend widget, ensuring the NTE status displayed in Fexa accurately reflects the system's check.

 

Removing Asset from Work Order Triggers Error

When a work order was created with an asset assigned, users were unable to remove that asset without encountering an error. The system was incorrectly enforcing that at least one asset must remain on a work order at all times, even when the asset had been added in error or was no longer relevant.

What's Fixed:

  • Users can now remove an asset from a work order and save successfully without any errors.