This chapter provides an overview of how the Datatables feature, introduced in version 2026_1, provides a direct view into the transactional data tables used by interfaces and billing tasks. These tables contain the raw data that Good Sign receives before objects, charges, or enrichments are created.
Figure 1: Datatables menu item in the Interfaces section
Datatables are especially useful for:
- Inspecting and validating imported data
- Debugging issues in integrations or billing tasks
- Understanding how raw data transforms into final business objects
- Identifying data quality or structural problems early
The Datatables grid is optimized for large datasets, supporting paging, server‑side filtering, grouping, and customizable views.
2. Required User Rights
To see the Datatables menu, users need the following right:
- auth_right_id 3336 — Menu → Interfaces → Datatables
With this right, users can view all datatables that interfaces generate.
Table‑specific access restrictions can be configured by a Good Sign consultant when needed.
3. What Datatables Represent
Whenever an interface receives data, the system stores that data in a datatable that matches the interface name. For example:
- EventDataImport receives event data → datatable named EventDataImport
- OrganizationImport receives organization rows → datatable named OrganizationImport
Figure 2: Example datatable created from an incoming interface (EventDataImport)
These tables contain the raw incoming rows exactly as received—before Good Sign enriches, aggregates, or creates customer, contract, or billing objects.
This allows users to:
- Confirm that data has arrived
- See how many rows were received
- Validate that key fields are populated
- Identify malformed or incorrect records before processing occurs
4. Grid View
The Datatables grid provides several tools for navigating and analyzing data.
4.1 Paging
Data is shown in pages. Increasing the number of rows per page is helpful when filtering and grouping large datasets.
4.2 Sorting
Click a column header to sort the table ascending or descending.
4.3 Filtering
Filters can be applied directly from the grid.
Filtering is handled server‑side to ensure good performance even with large tables.
Figure 3: Applying filters directly in the Datatables grid
4.4 Grouping
You can group data by dragging a column into the grouping area.
Figure 4: Grouping data by dragging a column into the grouping bar
Note:
Grouping is applied only to the rows currently loaded on the page.
For reliable grouping results, increase the number of items per page and pre‑filter the dataset.
5. Typical Use Cases
Datatables support a wide range of practical scenarios.
5.1 Validating Imported Data
After running an import (e.g., OrganizationImport, PriceImport, ContractLineImport), Datatables allow you to:
- Verify the number of imported rows
- Check that field values match expectations
- Confirm that your file content was interpreted correctly
5.2 Debugging Integration Issues
If objects were not created as expected, Datatables help you confirm:
- Whether the interface received the data
- Whether mandatory fields were populated
- Whether identifiers or mapping values are correct
5.3 Inspecting Usage or Event Data
For usage‑based billing, Datatables allow daily/weekly validation of:
- Transaction IDs
- Quantities
- Product codes
- Mapping values
This helps ensure correct downstream billing.
5.4 Preparing Corrective Actions
If rows require exclusion or additional enrichment before processing, Good Sign consultants can build custom events or transformations based on the datatable contents.
6. Custom Actions (Consultant Driven)
Good Sign consultants can add customer‑specific actions to the Datatables interface, such as:
- Excluding rows from processing
- Adding enriched or derived columns
- Creating status descriptions
- Attaching custom validation or correction steps
- Adding menu commands (edit, cancel, delete)
These actions are implemented by Good Sign consultants and tailored to each customer’s requirements.
7. Datatables and Interfaces — How They Work Together
Datatables complement the Good Sign import interfaces:
|
Feature |
Interfaces |
Datatables |
|
Purpose |
Import and process data |
View and validate raw incoming data |
|
Data |
Transformed into business objects |
Untouched raw rows |
|
Usage |
Handling imports and API flows |
Troubleshooting, validation, QA |
|
When used |
Before/after processing |
Before object creation or during debugging |
Datatables do not replace interfaces—they provide visibility and control around them.
8. Customizable View Options
Although end-users cannot configure datatables themselves, it is useful to understand what is possible through consultant configuration:
- Controlling which tables are visible to whom
- Setting default columns and column order
- Setting default sorting
- Excluding unnecessary or sensitive fields
- Adding enrichment from other tables (e.g., readable status values)
- Adding dynamic or calculated fields
These customizations help tailor the Datatables experience to customer-specific needs.
9. When to Contact a Good Sign Consultant
You should reach out when:
- You need enrichment or calculated fields
- You notice a table includes sensitive or irrelevant columns
- You require table‑specific access rights
- You want a custom action added to a table
- You need corrections to the way data is processed downstream
Datatable configuration often affects underlying SQL metadata and should only be performed by Good Sign consultants.
10. Summary
Datatables give users a powerful, transparent view into the raw transaction-level data that drives Good Sign's billing and contract automation. They are essential for:
- Validating data imports
- Debugging integration issues
- Inspecting usage and event data
- Ensuring data quality before billing
- Supporting collaboration between customers and consultants
With intuitive sorting, filtering, grouping, and customizable enhancements, Datatables help users quickly understand and verify the data flowing into Good Sign.