Inverse Watch Docs
AppLanding
  • Overview
    • Home
    • Governance
      • Proposal 7
      • Proposal 25
      • Proposal 52
      • Proposal 107
      • Proposal 147 - S1
      • Proposal 189 - S2
  • Products
    • Inverse Alerts
      • See on Twitter
    • Inverse Chatbot
      • /doc
      • /imagine
      • /data
      • /graph
    • Inverse Subgraphs
      • See inverse-subgraph on Mainnet
      • See inverse-governance-subgraph on Mainnet
    • Inverse Watch
      • Go to App
  • User Guide
    • Quickstart
    • Alerts
      • Setting Up an Alert
      • Adding New Alert Destinations
      • Customize Alert Template
      • Multiple Column Alert
    • Queries
      • Creating and Editing Queries
      • Querying Existing Query Results
      • Query Parameters
      • How to Schedule a Query
      • Favorites & Tagging
      • Query Filters
      • How To Download / Export Query Results
      • Query Snippets
    • Visualizations
      • Cohort Visualizations
      • Visualizations How-To
      • Chart Visualizations
      • Formatting Numbers in Visualizations
      • How to Make a Pivot Table
      • Funnel Visualizations
      • Table Visualization Options
      • Visualizations Types
    • Dashboards
      • Creating and Editing Dashboards
      • Favorites & Tagging
      • Sharing and Embedding Dashboards
    • Data Sources
      • CSV & Excel Files
      • Google Sheets
      • JSON (API)
      • Python
      • EVM Chain Logs
      • EVM Chain State
      • GraphQL
      • Dune API
    • Machine Learning
      • Data Engineering
      • Regressors
        • Linear Regression
        • Random Forest
        • Ada Boosting
        • Gradient Boosting
        • Neural Network (LSTM)
      • Training and Predicting
      • Metrics & Overfitting
      • Examples
        • Price Prediction
          • Data Preprocessing
          • Model Creation & Training
          • Metrics Evaluation
          • Back Testing
          • Visualizing
        • Liquidation Risk
  • Admin & Dev Guide
    • Setup
    • Redash
    • Integrations & API
    • Query Runners
    • Users
      • Adding a Profile Picture
      • Authentication Options
      • Group Management
      • Inviting Users to Use Redash
      • Permissions & Groups
    • Visualizations
  • Cheat Sheets
    • Snippets
    • Contracts
  • More
    • Deprecated Apps
    • Github : inverse-flaskbot
    • Github : inverse-subgraph
    • Github : inverse-watch
Powered by GitBook
On this page
  • 1. Using Tables
  • 2. Formatting Columns

Was this helpful?

  1. User Guide
  2. Visualizations

Table Visualization Options

PreviousFunnel VisualizationsNextVisualizations Types

Last updated 1 year ago

Was this helpful?

1. Using Tables

For data sources that support a native query syntax (SQL or NOSQL), you can choose your data return format, which columns to return, and in what order by modifying your query. But sources like CSV files or Google Sheets don’t support a query syntax. So the application allows you to manually reorder, hide, and format data in your table visualizations.

If you absolutely depend on a feature of SQL, you can use the to post-process your data.

i. Visualization Settings

To get started, click the Edit Visualization button under the table view. A settings panel appears that looks like this:

You can:

  • Reorder Columns by dragging them to the left or right as shown in the yellow highlight.

  • Hide Columns by toggling the check.

  • Format Columns using the format settings. Read more about column formatting below.

2. Formatting Columns

The application is sensitive to the data types that are common to most databases: text, numbers, dates and booleans. But it also has special support for non-standard column types like JSON documents, images, and links.

The application sanitizes HTML in query results. But if any HTML tags remain they are not escaped by default. Thus you may see odd effects if a query result includes string fields that include HTML (e.g. from a web scraper). Toggle the Allow HTML content setting in the visualization editor to escape HTML characters.

i. Common Data Types

The application will render a column as text if your underlying data source does not provide type information. But you can force it to use arbitrary types using the table visualization editor. This is especially useful for sources like SQLite, Google Sheets, or CSV files where type data is not available. You can, for example:

  • Display all floats out to three decimal places

  • Show only the month and year of a date column

  • Zero-pad all integers

  • Prepend or Append text to your number fields

ii. Special Data Types

The application also supports data types outside the common database specifications.

  • JSON Documents

  • Images

If a field in your database contains links to an image, the application can display that image inline with your table results. This is especially useful for dashboards.

In the dashboard below, the avatar image field is a URL to a picture which the application displays in-place.

  • HTML Links

Just like with images, HTML links from your DB can be made clickable in the application. Just use the Link option in the column format selector.

A full reference for rendering numbers in the application is available . You can read about how to format dates .

A full reference for rendering numbers in the application is available . You can read about how to format dates .

If you’re underlying data returns JSON formatted text in a field, you can instruct the application to display it as such. This lets you collapse and expand elements in a clean format. This is particularly useful when querying RESTful APIs with the.

If you’re underlying data returns JSON formatted text in a field, you can instruct the application to display it as such. This lets you collapse and expand elements in a clean format. This is particularly useful when querying RESTful APIs with the

here
here
here
here
JSON Data Source
JSON Data Source
Query Results Data Source
visualization settings
Images
HTML links