Shared elements in table popups

Table popups in the Warehouse and the Lake share one set of building blocks: the banners along their tops, the windows they open, the cells and action strips in their grids, and the diagnostics behind their logs. Use this page as the quick reference for those shared pieces; each task page explains the work in full.

Banners and notices

A short strip, or a full card, tells you when a table is not ready for the work you opened it for.

• Deploy required. While a table is not deployed, its popup shows an amber strip with a Deploy action (the label becomes Deploying while it runs). A Dictionary reads "This dictionary is not deployed. Deploy to enable preview and statistics."; a Dimension reads "This Dimension table is not deployed. Deploy to enable statistics and transformation runs.". Fact and Static tables follow the same pattern. Deploying creates the table in the Warehouse from its current definition, so its preview, statistics and runs start working; see Deploy, run, truncate and monitor tables.
• Not deployed, in full. The Settings tab of an undeployed table shows the same state as a card: the title names the kind (Dictionary Not Deployed, Dimension Table Not Deployed, Static Table Not Deployed) and the body explains what deploying unlocks, for example "Deploy this dictionary to access preview and statistics. Deployment creates the table in the warehouse with your current configuration."
• Primary key missing. "Primary key required. Define a primary key column before this table can be deployed." A view reads the same sentence with "view" in place of "table". The strip offers Go to Columns; the action is hidden while you are already on the Columns step. The grid behind it, and its primary-key rules, are on The table columns grid.
• Dependants could not be determined. On the Dependants tab, a DataPrism part of the check that could not run shows a warning notice: "DataPrism dependants could not be determined because the check failed. Acting on the assumption that this table is unused may be unsafe." Treat the list as incomplete before you change or drop the table; see Dependants: what uses a table and Deleting a table with dependants.

Windows a popup opens

Every window below opens from a named control on the popup, and the control decides what the window is filled with.

• Manage Dependencies. On the Dependencies step, Manage (when dependencies already exist) or Manage Dependencies (in the No dependencies selected empty state) opens this window. A view's empty state adds "Choose tables your view depends on to give it the right upstream context.". The window is titled Manage Dependencies, holds the same table picker as Select context tables (titled Select dependencies here), and closes with Cancel or Done.
• Query Data Preview. When a query you ran in a popup editor returns rows, they open in Query Data Preview, with their types and the preview toolbar. With nothing to show it reads No data preview available ("There is no query result to display yet. Run the query to see its data here."); a query that ran but returned no rows reads No data available ("This query executed successfully but did not return any rows."). Downloads work as in any preview; see Table preview, filters and export.
• Query history. The History action in the query editor header opens a versions window: a Versions list on the left (newest first, each entry naming its author and showing a v{n} badge, Loading history... while it loads, No query history yet when there is nothing) and a detail pane on the right with the Query and Compare tabs. Compare shows the chosen version against Current Query; Replace puts the chosen version back into the editor, and Copy query copies its text. Versions are recorded as the popup's query is validated.
• Query Validation Error. When a query fails to validate, this window shows the error and offers Fix with AI, with an optional Additional Context (optional) box ("Add any additional context about what you were trying to do..."). The suggestion does not replace anything on its own: it opens in Query Difference Checker as a diff, with Current Query on one side and AI Suggested Query on the other; Apply Changes puts it into the editor.
• Error Details and the stack viewer. A popup's error strip shows the message with a View details action; both the strip and the action open Error Details, where the full text sits with Copy Error (the label turns into Copied once copied). In the log grids, the error cell opens the same kind of window with the stack: it is titled Error Stack Trace, or Runner Diagnostics when there is a report but no stack. Copy takes the stack text and the report together.
• Refresh settings guide. In a Dictionary or View popup, the book icon beside the Refresh Settings header (tooltip Refresh settings guide) opens Refresh Settings, a short guide to the refresh interval, its offset, the retries and where the refresh runs. Got it closes it.

Grid cells and row actions

The grids inside popups use a small set of cells that keep values readable and easy to copy.

• Copy cells. Click a value to copy it; the copy icon turns into a tick for a moment. Ids, notes and plain text cells work this way, and a long value shows its full text on hover.
• Value formats. A date shows as dd/MM/yy · HH:mm:ss; a rows count groups thousands (1,234); a duration reads like 2m or 1h 5m 3s and counts up by the second while its run is still live.
• Status cell. The run's state in colour and icon: a spinner while it is running or pending, a tick for a finished run, an alert mark for a failed one, a muted mark for cancelled and aborted runs.
• Row actions. A running row offers a stop control (Abort synchronization in a staging table's Sync Log); it opens a confirmation titled Abort Synchronization before the run stops. A settled row can offer a delete control (Delete log entry) with a Delete Log Entry confirmation.
• Open in Editor. A popup's query header can carry Open in Editor (tooltip Open in Query Editor). It minimises the popup and opens the query editor in a new console named after the popup, filled with the current query; it is greyed out while the query is empty.
• Compact action strips. Section headers gather their actions as a strip of small buttons, for example Synchronize, Truncate, Refresh, Deploy and Delete. A disabled action explains why in a tooltip rather than staying silent.
• Statistics cards. Below such a header sit tinted cards with a label and a value, for example Size, Rows and Partitions. While the table holds temporary data, a card adds a Temp line next to its value.

Sync-log diagnostics

A load that runs through an ANY API connector keeps its loader's report on the log row. This is where you read it; the log itself, with its runs and actions, is covered on Staging tables: conditions, sync and deploy.

1. Click the row's error cell (it previews the first line of the message), or the amber badge on a row that finished with warnings. The badge reads UTF-8 replaced: 4 when the count is known, or 3 warnings otherwise.
2. Read the report:
   • The headline names the outcome: Load failed or Load finished with warnings, with the loader's short identifiers (Runner, CDK, Mode, Stream) and the totals (Pages, Rows, Elapsed, Parallel). Elapsed shows seconds to one decimal, for example 12.3 s.
   • A Page section describes the page request (Params, Index, Token, URL); an HTTP section shows Status, Content-Type and Bytes.
   • A Decode section appears when a response could not be read: Kind names it (Invalid UTF-8, Invalid JSON, HTML body, Empty body), with the Error, the Byte position (or Char), the Bad bytes in hex (for example 0xED 0xA0 0x80) and a short context block.
   • A Warnings section lists one card per warning, with First at byte, Bytes, Page and Pages for its first occurrence, and the affected records (each line ends with -> field). A long record list ends with ... more records not listed.
   • A Log tail (N) fold shows the last lines the loader printed.

An empty log reads No synchronization logs found.

• The UTF-8 warning counts exactly: <n> invalid UTF-8 sequences replaced in <m> records, with singular forms ("1 invalid UTF-8 sequence replaced in 1 record") and <m>+ when the record list is cut short. The run still loaded the data; the loader replaced the invalid byte sequences it met.
• When you may not read the table's data, the record keys are replaced with [hidden: no data access] instead of values.

Stop a running check

While a query validation runs in a popup, the Validate button in the query editor header becomes Stop (tooltip Stop validation). Stop cancels the check itself on the server, so it stops running instead of finishing quietly in the background; closing the popup also cancels it. A cancelled check is not a failure: run Validate again when you are ready.

Questions, answered

What does a "not deployed" message mean?

The table's definition exists, but the table itself has not been created in the Warehouse yet. Until you deploy it, its preview, statistics and runs stay unavailable, so the popup shows the strip (with Deploy) and the card. Deploying creates the table from its current definition; the day-to-day deploy, run and truncate tasks are on Deploy, run, truncate and monitor tables.

Why does a banner ask me to define a primary key?

Deploying needs a primary key column, so the popup points at the fix instead of offering a deploy that would be refused. Go to Columns takes you to the columns grid, where you mark one column as the primary key; the action disappears while you are already on the Columns step. See The table columns grid.

What opens the Manage Dependencies window?

The Dependencies step of a View or Transformation popup. Click Manage when the step already lists dependencies, or Manage Dependencies in the empty state. The window holds the same picker as Select context tables, so you can search, select and manage source systems in one place; close it with Cancel or Done.

What does "No dependencies selected" mean?

It is the empty state of the Dependencies step: nothing has been picked yet, and that is normal until you choose tables. A view's line reads "Choose tables your view depends on to give it the right upstream context.". Click Manage Dependencies to open the picker.

Where do I see the result of a query I ran in a popup?

It opens itself: a query that returns rows shows them in Query Data Preview as soon as it finishes, with the columns' types and the preview toolbar. If the window says No data available, the query ran but returned no rows; if it says No data preview available, there is no result to show yet. Downloads work as in any preview; see Table preview, filters and export.

How do I get an earlier version of a query back?

Open History in the query editor header. The left side lists the Versions (newest first, each with its v{n} badge); pick one to read it, use Compare to see it against Current Query, and click Replace to put it back into the editor. Copy query copies it if you only need the text.

What is the Query Validation Error window?

It appears when a query fails to validate: it shows the error and offers Fix with AI, with an optional box where you can add context about what you were trying to do. The suggestion does not replace anything on its own: it opens in Query Difference Checker as a diff, and Apply Changes puts it into the editor.

Where do I read the full error behind a Sync Log row?

Click the row's error cell. The window shows the message in full, and when a stack exists it is titled Error Stack Trace, with the loader's report above the stack; a report without a stack opens as Runner Diagnostics. Copy takes both together, so you can share them as one text.

What does "UTF-8 replaced: 4" mean?

The load met invalid UTF-8 byte sequences in the source and replaced them so the run could finish; the badge counts the sequences it replaced. Open the row's report to read the exact sentence, like 4 invalid UTF-8 sequences replaced in 2 records, and to see which records were affected.

What does "[hidden: no data access]" mean?

The loader's report hides the keys of the affected records because you may not read the table's data. It is a privacy guard, not an error: if you need the values, ask a colleague who can read the table.

Does Stop really cancel the running check?

Yes. Stop cancels the validation on the server, so the check stops running instead of finishing in the background; leaving the popup cancels it too. A cancelled check is not recorded as a failure, so you can simply validate again.