Skip to content
Contact us
  • There are no suggestions because the search field is empty.

How to Use URL Parameters in NextTables Views

You will learn

NextTables view URLs accept parameters that pre-configure how the view loads — filtering rows, sorting, hiding fields, and switching to embed mode. Use these parameters to drop a pre-filtered, context-aware table directly into a BI dashboard, intranet page, or any application that supports iframes or embedded web objects.

Prerequisites

  • A published NextTables view URL (the /view/<view-id> portion of the URL).
  • The field names of the table, exactly as they appear in the table header. Parameters reference fields by display name.
  • For embedding: a host application that supports iframes or embedded web objects (for example, Power BI, SAP Analytics Cloud, or Tableau).

Supported URL parameters

NextTables supports four URL parameters. You can combine any of them in the same URL using & as the separator.

Parameter Purpose
embed Loads the view without the sidebar and top navigation bar — ideal for embedding inside another application.
filter Filters rows by one or more field values.
hide Hides one or more fields from the table.
sort Sorts the table by one or more fields, ascending or descending.

💡 Tip: The fastest way to build a parameterized URL is to configure the view directly in NextTables. Apply filters, sorting, and field visibility from the column headers in the table. The URL updates automatically as you change the view — copy that URL and replace the static values with dynamic ones supplied by your BI dashboard.

Step-by-Step Instructions

Build a parameterized URL from the NextTables UI

  1. Open the table view in NextTables.
  2. In the column header of a field, apply a filter, sort direction, or hide the field as needed.
  3. Repeat for every field you want included in the parameterized URL.
  4. Copy the URL from the browser address bar. The URL now contains the parameters that reflect the current view state.
  5. (Optional) Replace static values in the URL with dynamic placeholders supplied by your host application (for example, a BI dashboard filter value).
  6. Embed the URL using an iframe or web object in the host application, and append &embed to hide the NextTables chrome (see embed — Embed mode below).

💡 Tip: Two-way sync between the URL and the view works in both directions. Changing the view updates the URL, and loading a parameterized URL applies those settings to the view.

embed — Embed mode

Use the embed parameter to hide the NextTables sidebar and top navigation bar. The view renders only the table, so it integrates cleanly into another application.

Example

https://<workspace>.nextlytics.com/view/<view-id>?embed

📝 Note: Embed mode is designed for use inside iframes or embedded web objects in BI dashboards, intranet pages, and similar surfaces.

If the user is already signed in to NextTables, the embedded view loads directly. If not, a login screen appears first — with password, Microsoft, or Google sign-in available depending on how the NextTables instance is configured — and the user is then redirected to the embedded table.

sort — Sort the view

Sort the view by one or more fields. Each sort entry has the form <Field> ASC or <Field> DESC. Multiple sort entries are separated by ;. Field names with spaces or special characters are written as-is — no backslash escape and no URL encoding are required.

Syntax

sort=<Field1> ASC;<Field2> DESC

Example

?sort=Unit Price ASC;Approved DESC

This sorts rows by Unit Price ascending, then by Approved descending.

hide — Hide fields

Hide one or more fields from the table. Field names are separated by ;. Use this to remove fields the embedding context does not need — for example, a field that drives the BI dashboard filter but should not appear in the table itself.

Syntax

hide=<Field1>;<Field2>

Example

?hide=Customer Name;Order Quantity

This hides the Customer Name and Order Quantity fields from the table.

💡 Tip: Combine hide and filter on the same field to deliver a focused experience. Filter the table to the rows that match the user's dashboard selection, then hide that field so it does not take up space in the embedded view.

 

filter — Filter rows

Filter rows by one or more field values. Each filter entry has the form <Field> <operator> <value>. Multiple filter entries are separated by ;. Field names and string values are written as-is — no escaping and no URL encoding (such as %20 for spaces or %22 for quotes) are required, though raw and URL-encoded values are both accepted.

Supported operator

Currently, only the equality operator eq is supported. Additional comparison operators are on the roadmap and are not available today.

Multiple values for the same field

To match a field against multiple values, chain repeated eq statements for the same field with ;. The view returns rows where the field equals any of the listed values.

Example

?filter=Status eq "Open";Status eq "In Review"

This returns rows where Status equals either Open or In Review.

Value formats by data type

Data type Format Example
Text Value in double quotes Customer Name eq "Acme Corp"
Number (integer) Raw number, no quotes Order Quantity eq 250
Decimal number Raw number, no quotes Unit Price eq 149.9900000000
Boolean true or false, no quotes Approved eq true
Date "YYYY-MM-DD" in double quotes Order Date eq "2024-01-03"
Time "HH:MM:SS" in double quotes Cutoff Time eq "11:15:00"

Syntax

filter=<Field1> eq <value>;<Field2> eq <value>

Example (combining all data types)

?filter=Customer Name eq "Acme Corp";Order Quantity eq 250;Approved eq true;Order Date eq "2024-01-03";Cutoff Time eq "11:15:00";Unit Price eq 149.9900000000

📝 Note: Additional filter operators beyond eq are on the NextTables roadmap. For dashboards being built today, design integrations around equality filters.

Use case: a context-aware table inside a BI dashboard

The most common reason to use URL parameters is to embed a NextTables view inside a BI dashboard so that the table always reflects the same rows the user is currently analyzing.

  1. In NextTables, configure the view with the filters, sorting, and hidden fields you want as the default state.
  2. Copy the URL from the browser address bar.
  3. Append embed to hide the sidebar and top navigation.
  4. In the BI dashboard (for example, Power BI, SAP Analytics Cloud, or Tableau), add an iframe or embedded web object pointing to that URL.
  5. Replace the static filter values in the URL with dynamic values supplied by the dashboard's filter or selection (using the BI tool's own placeholder syntax).
  6. Hide the filter field with hide=<Field> so it does not appear in the embedded table — the dashboard itself already shows the selection.

Example

https://<workspace>.nextlytics.com/view/<view-id>?embed&filter=Region eq "<dashboard-region>"&hide=Region&sort=Order Date DESC

When the dashboard user changes the Region filter, the embedded NextTables view updates to show only the rows for that region. Every edit a business user makes inside the embedded table is validated, authorized, and auditable, with governed write-back to the enterprise data platform.

Complete example

A URL that combines all parameters:

https://<workspace>.nextlytics.com/view/<view-id>?filter=Customer Name eq "Acme Corp";Order Quantity eq 250;Approved eq true;Order Date eq "2024-01-03";Cutoff Time eq "11:15:00";Unit Price eq 149.9900000000&hide=Customer Name;Order Quantity&sort=Unit Price ASC;Approved DESC&embed

This URL:

  • Filters by six fields (one per data type) using the eq operator.
  • Hides the Customer Name and Order Quantity fields from the table.
  • Sorts by Unit Price ascending, then by Approved descending.
  • Loads in embed mode (no sidebar, no top navigation).

Troubleshooting / FAQs

Q: A field name in my URL is not being recognized. What should I check?

A: Field names must match the display name of the field in the table header exactly, including capitalization. Spaces and special characters can be used as-is — no backslash escape or URL encoding is required, although URL-encoded values are also accepted.

Q: Why does my filter return no rows?

A: Check the value format for the field's data type — see the Value formats by data type table above. Common causes are missing double quotes around text, date, or time values; using quotes around boolean or numeric values; or supplying a date or time in a non-ISO format.

Q: Are operators other than eq available?

A: Not today. Additional operators are on the NextTables roadmap. For dashboards being built today, model the integration around equality filters.

Q: The URL does not update when I change filters, sorting, or hidden fields in the view.

A: Make sure you are on a view URL (/view/<view-id>). Two-way sync between the URL and the view applies at the view level. If the URL still does not update, refresh the page and reapply the change.

Q: Can I reuse the same parameterized URL across different views?

A: No. Parameters apply to the specific view referenced by <view-id>. To pre-configure a different view, build the URL from that view's address.

Q: What happens if a user opens the embedded view without being signed in to NextTables?

A: A login screen appears in the embedded frame. The user signs in with password, Microsoft, or Google (depending on the instance configuration) and is then redirected to the embedded table.