Local Test Harness

VizJson to LSQL to Data/Table/Csv

Work through the flow from top to bottom: load a token and confirm the Analytics server, search for a workbook or paste VizJson manually, generate logical SQL, then run the SQL and inspect the returned rows as a table or CSV.

Step 1

Load Token And Identify Server

Drop a token.json file, inspect the token details, and confirm which Analytics base URL should be used for execution.

Drop token.json here Or click to choose a token file. The page keeps it in memory and sends it only to the local tester server when you inspect or execute.
No token loaded yet.
Run the local helper with node serve-vizjson-tester.js and open http://localhost:4173 so token inspection and SQL execution can talk to the local Node server.
Step 2

Input VizJson

Search for a workbook, ask an AI agent a question, or paste VizJson manually into the editor below.

Source
Load a token in Step 1, then search for a workbook or paste VizJson manually.
Search for a workbook to fetch its VizJson. Once it is loaded, you can copy it or place it directly into the VizJson editor below.
Tip: use Ctrl+Enter to generate the current LSQL after you finish editing.
Step 3

Generate Logical SQL

Choose how the VizJson should be converted, then generate the LSQL and tweak it here if you need to test a manual variation before Step 4.

Output Mode
Ready. After you paste VizJson, click Generate LSQL.
You can edit this SQL before Step 4. For multi-statement output, keep the -- Query: Label line above each statement if you want to run all statements or pick one at a time.
Step 4

Run SQL And View Results

Execute the current LSQL output through the local SOAP helper, choose whether to run all generated statements or just one, switch between result sets when there are multiple queries, inspect the rows as a table or Oracle JET chart, and download the selected result as CSV.

Execution results will appear here after SQL is run.
Current mode: merged. Generate LSQL first, then run it here.
Run SQL to see tabular results.
No results yet. When execution succeeds, the selected result set will render as a table here.