Import refreshes a connected table from its source. It writes current source data into every scenario you have included, leaves the scenarios you have frozen alone, and never deletes a row or touches a column you added. Only you running Import ever imports data: saving a mapping, changing a setting, adding a scenario, or copying one never pulls from the source on its own.
What you can use it for
- Refreshing the roster before a forecast cycle. One Import updates every included scenario at once.
- Freezing an approved plan. Turn Included in import off for the Budget scenario and later Imports skip it, while Forecast keeps moving.
- Tracking what changed. Background Tasks and the Import log on the Connection Overview show every run, and the result names each scenario updated or skipped.
- Carrying your planning data through source changes. Rows that leave the source or stop matching your filter are kept, with their custom columns, as Out of Sync.
Before you start
- Running Import and opening the Connection Overview need Integrations access. Changing Included in import or editing rows follows the table's edit access.
- Map every dimension column before your first Import (see Map Dimension Columns in a Connected Table). An Import that finds unmapped values stops without writing.
- Scenarios set to Write Protection: Blocked are always skipped, whatever their Included in import setting. Scenarios set to Write Protection: Actuals or Write Protection: AI Enabled are updated normally while included.
How to run an Import
1. Open the connected table.
2. Select Import. A banner reads "A table refresh is currently in progress. You can track its status from Background Tasks."
3. Select Background Tasks on the banner to watch the run. The Planning Table Import moves from Syncing to Import, and finished runs appear under History as Completed or Failed.
4. When the run completes, the table fills in and the Last import time updates in the scenario pane.
Import stays available while you are viewing a scenario that will be skipped. The run covers the other scenarios, and the result explains what was skipped.
Working with scenarios
Which scenarios an Import writes to
Import writes to every bound scenario that has Included in import on and is not Blocked. It skips the rest and names each one in the result as "not included in import" or "write protected". If no scenario qualifies, nothing is written and the table tells you why.
Freezing a scenario
In the scenario pane, select the scenario and switch the Included in import toggle. It is on by default for every scenario, there is no confirmation, and switching it never starts an Import. Rows in an excluded scenario stay editable.
Below the scenario selector, Last import [date] at [time] shows when that scenario last received data: green with a check when the scenario is included, orange with a minus when it is not. A scenario that has never been imported into shows nothing.
Adding, copying, and removing scenarios
The ⋮ menu in the scenario pane holds Copy to Scenario, Export, and Remove Scenario. The scenario dropdown holds Add Scenario.
- Add Scenario binds the table to a scenario with no rows. Select the scenario, then Add Scenario, and run Import to fill it with current source data. Blocked scenarios cannot be added. The drawer tells you who gains access to the table through the new scenario.
- Copy to Scenario makes an exact copy of the scenario you are viewing into a scenario the table is not yet bound to: every row with its state, every custom column value, and the Included in import setting. Choose the Original Scenario and the Copy to Scenario, then confirm. Only scenarios with No Write Protection can receive a copy. The copy does not call the source. Run Import afterwards if you want the new scenario brought up to current data.
- Remove Scenario unbinds the scenario you are viewing from the table and deletes that scenario's rows from it. The other scenarios are untouched.
How Cube decides what happens to each row
Every row in a connected table carries a Source Status of Synced, Out of Sync, or Manually added. Import never deletes rows.
| State | Meaning | What you can edit |
|---|---|---|
| Synced | The record was in the source and passed your filter rules and mapping on the most recent Import | Custom columns only. Source columns are read-only. |
| Out of Sync | The row was imported before but no longer qualifies: it left the source, failed a filter rule, or its dimension value is now mapped to Ignore. It keeps every value. | Custom columns. The row can also be deleted. |
| Manually added | You created the row in Cube. Import never changes it. | Every column |
On each Import, Cube checks every source record against your filter rules and mapping. Records that qualify and are new become Synced rows. Records that qualify and are already in the table stay Synced with refreshed source columns. Synced rows that no longer qualify move to Out of Sync. Out of Sync rows that qualify again (for example a rehire) return to Synced with their custom columns intact. Records that never qualified are never brought in and never show as Out of Sync.
Out of Sync rows still count in formulas that read the table. To exclude them, add a condition on Source Status.
How to read the Import log
Select the source name under the table title, or the Connection Overview icon in the header, to open the table's Connection Overview. The Source card shows the last synced time and a dimension sync action; the Mapping card shows the unmapped count; the Destination card lists the bound scenarios. Below them, the Import log lists this table's runs only.
Each row shows Date, Type, User, Scenarios, and Status. Status is Success or Failed with the reason. On a Success row, the Scenarios count opens a list of each bound scenario as Updated, Skipped: not included in import, or Skipped: write protected. Dimension syncs are not logged.
Examples
A routine refresh
A Paylocity Roster is bound to Actuals (Write Protection: Actuals), FY26 Plan, Budget (Included in import off), and Forecast v2 (Write Protection: Blocked). The analyst is viewing Budget and selects Import. Actuals and FY26 Plan update, Budget is skipped as not included in import, Forecast v2 is skipped as write protected, and three rows move to Out of Sync. The three are employees who left since the last Import; their notes and merit assumptions are still there.
Freezing the approved budget
The board approves the FY26 budget in March. The analyst opens the table, selects the Budget scenario, and turns Included in import off. Every later Import skips Budget. In June she turns it back on; nothing happens until she selects Import, which then brings Budget up to current data in one run.
A rehire
An employee left in February and her row went Out of Sync, keeping the planned promotion the team had entered. She is rehired in August and appears in the source again under the same Employee Number. On the next Import her row returns to Synced with refreshed start date and salary, and the promotion note is still on the row.
Other things to know
- Custom columns survive everything. Values you enter in columns you added are kept on Synced, Out of Sync, and Manually added rows through every Import.
- Calculated columns recalculate after every Import.
- Write protection and Included in import are independent. Changing one never changes the other. Removing Blocked from a scenario does not import into it; the next Import you run does, if it is included.
- Import log statuses are Success and Failed only. An Import stopped for mapping is a Failed run with that reason.
- Mapping and Table Settings changes wait for an Import. Saving them changes no rows until you select Import.
- The spreadsheet apps show the same data. In Excel and Google Sheets, the scenario dropdown lists only the scenarios bound to the table, and rows you add there save back to the table.