Connect a Postman API key to check your work
You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.
A view is a saved SQL query, and it's the heart of a dataset. Views use SQLite-compatible SQL for files and standard databases, and because the view stays fixed even if the files behind it change, everything built on top of it keeps working.
Filter and Compute With a View
Your first views answer two simple questions: which accounts are on the enterprise plan, and what does each invoice look like in one line?
-
If
billing-datais still open in the active tab from the previous step, stay there. Otherwise open it from the sidebar. Then click Create view. -
In the Create view dialog, enter the View name:
textenterprise_accounts -
Open the Sources dropdown, select
source_accounts, then click Create view. -
The view opens with its data table at the top and a Query editor underneath, pre-filled with
SELECT * FROM "source_accounts". The new view also appears under Datasets in the left sidebar. -
Replace the query in the editor with this one, click Run to see the result, then click Save:
view · enterprise_accounts SELECT accountId, company, regionFROM source_accountsWHERE plan = 'enterprise'; -
Create a second view the same way. Click Create view again and enter the View name:
textinvoice_summary -
Select
source_invoicesin Sources and click Create view. -
Replace the query in the editor with this one, then Run and Save. It builds a computed column with
||, SQLite's string concatenation:view · invoice_summary SELECT invoiceId, product || ' (' || status || ')' AS summary, amountFROM source_invoices; -
Check that each view's data table matches the table under its query above.
Troubleshooting: If you see no such table, the query is using a source name your dataset doesn't have. The tables are source_accounts and source_invoices. If you renamed a source, open its auto-generated view and copy the name from its query.
Join the Two Sources
This is where a dataset earns its keep. Accounts and invoices came from different file types, yet one query can combine them into the table you actually want to test with.
-
Click Create view and enter the View name:
textaccount_invoices -
Open the Sources dropdown and select both
source_accountsandsource_invoices, then click Create view. A view that joins two sources needs both selected. -
Replace the query in the editor with this one, click Run, then Save. It joins the sources on
accountIdand keeps only the invoices that were paid:view · account_invoices SELECT i.invoiceId, a.company, a.plan, i.product, i.amountFROM source_accounts AS aJOIN source_invoices AS i ON a.accountId = i.accountIdWHERE i.status = 'paid'; -
Check that the data table shows four rows, one per paid invoice, each with the company name and plan.
A view can combine file sources and standard databases (MySQL, Postgres, SQL Server) freely, but a custom JDBC source can't be combined with other source types: its views use that database's own SQL dialect and must work against that source alone.
Troubleshooting: If you get no rows, check that both sources store accountId the same way. In invoices.json the ids are strings ("1"), matching the CSV.