Data Management for REDA Objects
Importing, exporting, mass-updating, and cleaning up data are all standard Salesforce capabilities — Data Loader, the Data Import Wizard, data export — so this article keeps those mechanics short and points to Salesforce's documentation. What it covers in full are the gotchas unique to REDA's data model: the system-managed fields you must never set on import, the records REDA guards against deletion, and the fact that REDA's automation fires on Data Loader loads too. After reading, you'll be able to bulk-load and export REDA data safely — without corrupting system-managed state or fighting the automation.
Access you'll need. Salesforce data-management rights (Data Export, Bulk API Hard Delete, or Modify All Data as applicable) — org-side. Plus REDA object access for what you touch: loading deals needs Opportunity create and edit from REDA - Property Leasing User or REDA - Master Data - Admin; loading Properties needs Property create and edit. Deleting is narrower — Opportunity delete is limited to Master Data Admin or Property Leasing User; Property delete to Master Data Admin only.
Which REDA objects you'll load
The high-volume REDA objects an administrator typically loads are:
- Property, Opportunity (the deal, lease, or sale record), and Inquiry (the prospect record).
- Opportunity Charge and Opp Invoice — the money records beneath a deal.
- Master data: Region, Charge Code, Amenity Code, Settlement Code, Leasing Rule, Commission Rule, Inflation Rule, Property Type, and Property List.
An edition note: on the Sales Cloud (ISV) edition the prospect, deal, service, and marketing records are standard Lead / Opportunity / Case / Campaign; on the Platform (OEM) edition they are REDA's custom Inquiry / Opportunity / Service Request / Promotion. Load against your edition's object.
Gotcha 1 — system-managed fields (don't touch)
Many REDA objects carry system-managed helper fields — fields the automation writes for itself. Setting them on import corrupts REDA's internal state. The rule is simple:
The system-managed field families to leave blank:
| Field (label) | Appears on | Why it's system-managed |
|---|---|---|
| SYS Currency | Account, Contact, Opportunity, Property, and most REDA objects | Stamped from the record's currency by automation when multi-currency is on |
| Auto Created (Sys) | Opp Invoice (and auto-generated invoices) | Marks records the automation created |
| Opp Invoice Batch SYS | Opp Invoice | Batch-membership flag |
| SYS Is Posted | Expense Reconciliation Line | Set by the Post / Unpost process |
| Next Recurring Invoice Date SYS | Opportunity Charge | The key the recurring-invoice job matches on |
| SYS Month / SYS Period | Inflation Rule Entry | Computed period keys |
| Key Definition ("DO NOT EDIT") | REDA CMS content | Internal mapping key — do not populate |
Gotcha 2 — automation fires on import
A bulk load into a REDA object is not inert. REDA's automation runs on any data change, including loads through Data Loader and the API — and there is no bypass mechanism: no setting turns the automation off for a load. That has real consequences:
- When multi-currency is on, importing records stamps the currency from REDA's SYS Currency field.
- Booking and expense flows can auto-create Opp Invoices as a side effect of a load.
- Closing a sale writes ownership trails.
Because the automation always runs, a row that violates a REDA validation rule — say, an Opportunity advancing to a gated stage without its required fields — is rejected row by row, with REDA's own message. Plan loads in small batches and in dependency order, and expect to read validation messages as you go.
Gotcha 3 — deletion is guarded
Several REDA records are protected from deletion by automation. Attempting to delete one returns REDA's own message, verbatim:
"This Opp Invoice Batch cannot be deleted."
"Expense Reconciliation Line cannot be deleted. Please unpost the batch prior to make any changes." — while the batch is Posted
"You cannot delete this record. Record is locked for editing." — the generic lock
Active Portfolio Accounts and Opportunity Charges carry deletion-prevention too. And even where deletion is allowed, it's narrow: Opportunity delete is limited to Master Data Admin and Property Leasing User, Property delete to Master Data Admin only, and Tickets can't be deleted by anyone. When a delete is blocked, resolve the underlying state first — unpost the batch, detach the invoice — then try again.
Import sequence (dependency order)
Load in dependency order so every lookup resolves against a record that already exists:
This mirrors the setup roadmap (see The Setup Roadmap).
Export & storage
Exporting REDA data is standard Salesforce export — use Data Loader's export or the scheduled Data Export. REDA ships no separate export tool. Storage counts against the same Salesforce org limits as any other data; REDA adds no separate storage. One note worth knowing: CMS content files — the files you upload on a Property's Marketing tab — are Salesforce Files and count toward your org's file storage (see Managing CMS Content).
Worked example: loading 200 properties and their leases
Meridian Properties needs to bulk-load 200 properties (Meridian Court units and Harbour Tower) and then their leases:
Where to go next
- Customizing REDA Objects — custom fields and layouts on REDA objects.
- Creating Users & Granting REDA Access — the object access each load needs.
- Managing CMS Content — CMS files and how they count toward storage.
- The Setup Roadmap — the order to bring data in.
- Working with Multiple Currencies — how SYS Currency stamping works.
Frequently asked questions
Yes, but REDA's automation fires on every row — there is no bypass — and validation rules reject bad rows. Load in small batches, in dependency order, and read the validation messages.
No. Leave all system-managed fields blank — REDA fills them. Setting them corrupts the record's internal state.
They're deletion-guarded. You'll see "This Opp Invoice cannot be deleted." or "Expense Reconciliation Line cannot be deleted. Please unpost the batch prior to make any changes." Resolve the underlying state — unpost the batch, detach the invoice — then try again.
No. Use the standard Salesforce Data Export or Data Loader. REDA ships no separate export tool.
Yes — they're Salesforce Files and count toward file storage. REDA adds no separate storage of its own.
Was this article helpful?