Integrations · SaaS applications

SaaS application test data management

Business applications such as CRM, ITSM, HR and ERP systems hold some of the most sensitive records a company has, and their sandboxes are often refreshed from production.

SaaS test data has to respect API limits and object relationships defined by the vendor, and must never route application payloads through a third party.

What test data management needs here

API-only, read-only extraction with OAuth or service accounts given as secret references.
Pagination and rate-limit handling, and incremental extraction where it is safe.
Object and relationship discovery so a subset keeps records connected across objects.

How DataNivra approaches it

SaaS connectors are roadmap work. The design keeps payload rows inside your network and applies the same masking domains and certification as databases.
Whatever the system, row-level work happens in the DataNivra agent inside your network: only metadata, aggregates and evidence reach DataNivra Cloud.

SaaS applications: connector status (5)

2 of these connectors can be used today (available or in preview); the others are shown with their honest status. Statuses are derived from recorded conformance evidence.

Available now

Salesforce

Shipped in the standard agent and backed by recorded conformance evidence.

Salesforce connector: object discovery through the REST describe API (Id as key, single-target lookups as relationships), SOQL query and queryMore reads with a pinned API version, and the org's daily API budget respected.

Available now — details about Salesforce

Available now

ServiceNow

Shipped in the standard agent and backed by recorded conformance evidence.

ServiceNow connector: table discovery from sys_db_object and sys_dictionary (inherited fields included, sys_id as key, reference fields as relationships) and Table API reads with a pinned API version.

Available now — details about ServiceNow

Coming next

Microsoft Dynamics 365

Active implementation; not yet available for production use.

Dynamics 365 (Dataverse) connector: table discovery from Dataverse metadata (primary id as key, single-target lookups as relationships), Web API reads with a pinned version and @odata.nextLink paging.

Coming next — details about Microsoft Dynamics 365

Coming next

SAP applications

Active implementation; not yet available for production use.

SAP S/4HANA connector over OData V2 and V4 APIs: entity sets, keys and referential constraints discovered from each service's $metadata, and counted, key-ordered reads.

Coming next — details about SAP applications

Coming next

Workday

Active implementation; not yet available for production use.

Workday connector: custom reports (Reports-as-a-Service) discovered from their XML schema and REST collections with offset paging, read by an integration system user.

Coming next — details about Workday

Learn, try, then start

See the whole workflow — discovery, classification, masking, subsetting and certification — in the synthetic playground, then start a free trial. The product overview explains how the customer-resident agent and DataNivra Cloud divide the work.

Other categories: Databases · Data warehouses · Lakehouses · Object storage · Files · NoSQL · Mainframe · Streaming · APIs.