Introducing Relm Reports.

Using the add-in

Push-back to cloud

How to push edits made in the Relm Excel add-in back to your property workspace — conflict detection, change preview, and the round-trip with the cloud.

Relm TeamUpdated 3 min read
On this page

This page is the step-by-step UI flow for pushing edits from Excel back to Relm. For the conceptual overview, see Push-back from Excel.

Before you push

  • You imported the property's data via Import All Data.
  • You've made one or more edits in the Excel sheets (most commonly the Pro-Forma assumptions).
  • You're signed in to the same Relm account that owns the property.

Steps

  1. Open the Relm Pro taskpane.
  2. Make sure the property selector shows the right property.
  3. Click Push to cloud.
  4. Review the diff preview — every cell that will be pushed, with old/new values side by side.
  5. Confirm.
  6. The taskpane progress bar tracks each batch of cells syncing.
  7. On success, you'll see a "Synced" timestamp and an entry under History.

What gets pushed

  • Edited input cells — assumptions, line items, debt terms.
  • Per-year overrides — if you put an explicit value in a year that was previously a formula-derived cell, that value is pushed as an override.

What gets warned but not pushed

  • Edits to derived cells (EGI, NOI, NCF). Pushing these would corrupt the model. The diff preview shows them with a warning icon and they're skipped from the push.
  • Cells outside the standard pro-forma layout (a note in column Z). They live in your local workbook but aren't pushed.

You'll see the warnings in the diff preview; nothing pushes silently.

Conflict handling

If someone edited the same property in Relm during your Excel session, the diff preview shows the conflict:

  • Your Excel value on the left.
  • The cloud value (newer) on the right.
  • For each conflict, pick which wins.

Conflict resolution is per-cell. You can pick all-mine, all-theirs, or mix-and-match.

Lock acquisition

The push acquires the property's edit lock for the duration of the sync. If someone is in Edit Mode in Relm right now, the push fails with a clear "[user] is editing this property; sync canceled" message. Retry once they save and exit.

Audit trail

Every push creates a Version history entry tagged "Push-back from Excel" with your name and the count of changed cells. You can drill into the entry to see the per-cell diff.

Re-import after push

After a successful push, the cloud is the source of truth. If you re-import in the same session, you'll get back exactly what you pushed (plus any small canonicalization Relm did, like rounding to consistent precision). This is a good sanity check that the round-trip worked end-to-end.

Common issues

  • "Sync failed: stale lock." Someone took the lock between when you started Push and when the lock acquisition fired. Retry.
  • "Sync failed: validation error." A cell you edited has a value Relm can't accept (e.g. a negative LTV). Fix the cell and retry.
  • "Sync failed: property not found." The property was deleted from Relm while you were editing. Reach out to support if this is unexpected.

What's next

Was this article helpful?

Still need help?

Our team usually responds within one business day. Tell us what you're trying to do and we'll get you unstuck.

Relm Pro Help Center