At some points the NextTables URL can be modified to achieve different results, like enabling a fullscreen mode for tables or adding filters via the URL.
URL changes for fullscreen display
Available from NextTables version 8
With small changes to the URL, it is possible to create a fullscreen table view. In this view, the menu is disabled and the user can’t navigate to a different table. This feature comes in handy, if NextTables should be integrated into different applications, like a dashboard.
URL structure
https://{yourdomain}/#/{table_display_type}/{table}/{table_type}/
Possible table display types
The menu entry can be configured as a table or import view in the wizard. Both of these views can be changed into a full screen view.
Table Display Type |
Result |
tables |
Standard option with visible table and side menu |
table |
The table is visible, but the menu is hidden. The user can't navigate to a different table. |
imports |
Only the upload dialogue is shown. The user can’t see the underlying table. The side menu is visible. |
import |
Only the upload dialog is shown. The user can’t see the underlying table, nor the side menu. The user can’t navigate to a different table. |
Add filters to URL
Available from NextTables version 9
Filters can be added to the NextTables URL to open a specific table with a preset of global filters.This feature creates the opportunity to jump from external applications (like a dashboard) with chosen filters, directly to the table without re-adjusting the filters.
General rules
- It is possible to add multiple filters to one NextTables URL
- If the NextTables URL contains a template, the filters will be added on top and will not be overwritten
- If the NextTables URL contains a template with a variable and a filter value for the same field, the variable will be overwritten
- All existing and added filters are shown in the global filter and can be changed
URL Structure with filters
https://{yourdomain}/#/{table_display_type}/{table}/{table_type}/{template_id?}?filter={filter_expression};{filter_expression};....
- Parameter to add Filters: ?filter=
- The fieldname is always the technical name
- The URL can be created with blank characters (space) within the filter expression, the browser will convert the “space” into “%20”
Filter expression |
Operator |
{fieldName} {operator} '{value}' |
eq, ne, gt, lt, cp, np |
{fieldName} {operator} ('{value1},{value2}') |
bt, nb |
{fieldName} {operator} |
null, notnull |
{fieldName} {operator} ('{value1}','{value2}') |
in, nin |
Operators
Operator |
Description |
eq |
equal |
ne |
not equal |
gt |
greater than |
lt |
lower than |
cp |
contains pattern |
np |
does not contain pattern |
bt |
between |
nb |
not between |
in |
equal (multiple values) |
nin |
not equal (multiple values) |
null |
is null |
notnull |
is not null |
Examples:
- Add 2 filter values for one field
https://{yourdomain}/#/tables/MY_ADSO/DSO/?filter=CALYEAR eq '2020';CALYEAR eq '2021'
- Add 2 filter values for different fields
https://{yourdomain}/#/tables/MY_ADSO/DSO/?filter=CALYEAR eq '2020';/BIC/PROD_ID eq '9001'
- Add filter for between
https://{yourdomain}/#/tables/MY_ADSO/DSO/?filter=CALMONTH2 bt (‘4’,’9’)
- Add filter for notnull
https://{yourdomain}/#/tables/MY_ADSO/DSO/MYTEMPLATE001/?filter=/BIC/ACT_FLAG notnull
- Add filter for in
https://{yourdomain}/#/tables/MY_ADSO/DSO/MYTEMPLATE001/?filter=CALYEAR in '2018,2019'
Call add form with parameters
Available from NextTables version 11
With small changes to the URL, it is possible to call the add form directly. The add form behaves like the "new input" popup, but will not show the table.
Like table and import, the form has two display types.
Form Display Type |
Result |
adds |
Standard option with visible form and side menu |
add |
The form is visible, but the menu is hidden. The user can't navigate to a different table or forms within NextTables |
URL Structure with filters
https://{yourdomain}/#/{form_display_type}/{table}/{table_type}/{template_id?}?default={technical_field_name} eq {value};....
- Parameter to add Filters: ?default=
- The fieldname is always the technical name
- The add form only supports the 'eq' operator
- The fields are separated via a semicolon ;
- The URL can be created with blank characters (space) within the filter expression, the browser will convert the “space” into “%20”
Examples:
- Add one value for a field
https://{yourdomain}/#/add/MY_ADSO/DSO/?default=USER eq 'JOHNDOE01'
- Add one value for a InfoObject
https://{yourdomain}/#/add/MY_ADSO/DSO/?default=/BIC/COUNTRY eq 'GERMANY'
- Add two values for two fields
https://{yourdomain}/#/add/MY_ADSO/DSO/?default=USER eq 'JOHNDOE01'; CITY eq 'COLOGNE'
The URL can contain fields and InfoObjects at the same time.
Default scenarios, BAdIs and the add form
The default scenarios and custom BAdIs can be a big support for the add form and add a lot of utility. Please keep in mind, that both will always overwrite a value delivered by the URL.
Example:
The URL contains a value for the field USER but the a default scenario is configured for this field, where it is always filled with SY-UNAME. In this case the value coming from the URL will be overwritten with the value determined by the default scenario.
Which License is needed for this feature Professional ✔ | Enterprise ✔