Updating and maintaining data

How Google Sheets updates affect charts

Charts are directly connected to a Google Sheets data source. Any change in the sheet can impact the chart—either seamlessly or disruptively.

What updates automatically

• Changes to cell values (e.g. updated property prices or listing counts)

• Adding new rows within the existing structure

• Updating existing data entries

These changes are reflected after syncing the data source and do not affect the chart configuration.

What can cause issues

• Renaming columns (e.g. changing “Price” to “Listing Price”)

• Reordering columns

• Deleting columns used in the chart

These changes can break mappings between the chart and the dataset.

When a re-sync is required

Use the Sync data source button whenever:

• Data in Google Sheets has changed

• The data source URL has been updated

• You want to refresh the preview with the latest data

Expected system behavior (based on current logic)

• Sync all data sources

  • Reloads the preview page

  • Ensures the editor reflects the latest data

• URL change + same column names

  • Configuration is preserved

  • No reset occurs

• Column name changes (regardless of URL)

  • Configuration is reset

  • This applies even if only one selected column is affectedy if the data becomes invalid after syncing.

Ensure Google Sheets changes are fully saved before syncing

A common source of issues is syncing data before Google Sheets has fully saved the latest changes.

How to check the save status in Google Sheets

Google Sheets provides visual indicators in the top bar:

• “Saving…”

  • Changes are still being processed

  • Data is not yet reliably available for syncing

• “Saved to Drive”

  • Changes are stored in Google Drive

  • This is the minimum requirement before syncing

• Cloud icon with a checkmark

  • Confirms that all changes are fully synced and stable

  • This is the safest moment to trigger a data sync

Important limitation

Even when Google Sheets shows “Saved to Drive”, there can be short delays before the backend can access the updated data.

This means:

• The editor may still receive outdated data

• Recent changes may not appear in charts after syncing

How to recognize this issue

A strong indicator is the duration of the sync process:

• 1–2 seconds

  • Likely no real update happened

  • Backend did not detect the latest changes

• ~10 seconds or more

  • Data is being properly fetched and updated

  • Changes are more likely to be reflected correctly

Recommended workflow

Do’s

1. Wait until the status shows “Saved to Drive” and the cloud checkmark appears

2. Pause briefly (a few seconds) after saving before syncing

3. Trigger sync and observe the loading time

4. Make other changes (maybe in an unused sheet). Re-sync if the process was unusually fast and changes are missing

Don’ts

• Do not sync while the status shows “Saving…”

• Do not rely on immediate sync after making changes

• Do not assume a fast sync means a successful update

Risks of structural changes

Structural changes are the most common reason charts break.

High-risk changes

• Renaming columns used in chart mappings

• Removing required columns

• Changing column data types (e.g. numbers to text)

Why this matters

Charts rely on column names to map:

• X-axis (e.g. “Quarter”)

• Y-axis (e.g. “Average price”)

• Filters or categories (e.g. “Property type”)

If a column is no longer recognized, the chart cannot display correctly and must be reconfigured.

Recommended workflow

To safely update data without breaking live charts, follow this approach:

Do’s

1. Duplicate your Google Sheet before making structural changes

2. Test changes in the duplicated version

3. Only replace the data source URL once the structure is stable

4. Keep column names consistent whenever possible

5. Use sync to validate changes in the editor preview

Don’ts

• Do not modify column names in a live, connected dataset

• Do not delete or reorder columns used by charts

• Do not overwrite existing datasets without testing

• Do not assume small changes (e.g. one column rename) are safe

Example workflow (real estate use case)

Scenario: Updating a chart showing average property prices by district

1. Duplicate the original sheet:
   “Market Data – Berlin 2025” → “Market Data – Berlin 2025 (Update)”

2. Apply changes:

   • Add new districts

   • Adjust price values

   • Keep column names like “District” and “Average Price” unchanged

3. Test in the editor:

   • Update the data source URL

   • Click Sync

   • Confirm chart displays correctly

4. Replace the original only if everything works as expected

Handling outdated or unused datasets

Over time, multiple datasets may accumulate. Keeping them organized avoids confusion and errors.

Best practices

• Clearly name datasets (e.g. “Hamburg Prices Q1 2026”)

• Remove or archive unused sheets

• Avoid reusing old datasets for new purposes

• Document which charts depend on which data sources (if possible)

When to delete a dataset

• It is no longer connected to any chart

• A newer version has replaced it

• It contains outdated or incorrect data

Key takeaway

Treat your data structure as stable infrastructure.
Content (values) can change frequently—but structure (column names and layout) should remain consistent.

When structural changes are necessary, duplicate first, test thoroughly, and only then update the live connection.