Validate FDS subscriptions items as a provider
Configure the sample data received from the consumer to validate a foundation data sync (FDS) subscription item.
Before you begin
Role required: admin (sb_admin)
About this task
After you create an FDS offering request, the consumer acknowledges the request and sends you a sample payload. This payload helps you understand the structure and type of data you will receive.
After the consumer sends the sample, the system creates a subscription for each offering in the FDS request. Each subscription includes a subscription item for every table the consumer shares. Configure the incoming sample data to validate each subscription item.
Procedure
Navigate to All > Service Exchange Provider > Open Records > FDS Requests.
From the Type: Inbound, select the request.
From the Foundation Data Provider Inbound Subscriptions related list, open the provider subscription by selecting the record number in the Number column.
From the Subscription Items related list, open the subscription item by selecting the record number in the Number column.
Each subscription item represents a specific table that the consumer is sharing with you.
Resolve missing relationships on your instance.
When the source instance includes relationships that aren't present on your instance, the subscription item displays a warning banner.
Do the following steps to resolve the missing relationships:
Select Review and resolve.
In the Missing Relationships window, review the listed relationships, and select a resolution option.
- Fix automatically: The system creates the missing relationships to match the source instance.
Resolve manually: You create and configure the missing relationships.
Note: If you select Resolve manually, the ETL Transform Map Assistant doesn't automatically map the missing relationships. Create and configure them manually in the CMDB so that the data syncs correctly.
Select Confirm.
The system posts a work note recording the relationships it created or your manual resolution choice.
For unresolved relationships, the banner remains until you complete the configuration.
Configure incoming data using either IntegrationHub ETL or a transform map depending on whether you are working with a Configuration Management Database (CMDB) or a non-CMDB table.
| Option | Description |
|---|---|
| Configure data integration for CMDB tables |
A message is displayed stating that you're about to navigate to the ETL Transform Map Assistant guided setup.
The system creates a basic field mappings based on matching field names. Review and customize the mappings as needed for your instance. Note: Since FDS provides display values for reference fields, if you want to use reference data, you must create a table look up transform mapping to retrieve the Sys ID from the reference table. For more details, see Foundation Data Sync :: Known issues and workarounds [KB2299760]
|
| Configure data integration for CMDB tables (Maintain sysID enabled by the provider) |
A message is displayed stating that you’re about to navigate to the Transform Map to complete the configuration.
|
| Configure data integration for non-CMDB table |
A message is displayed stating that you're about to navigate to the Transform Map to complete the configuration.
|
You must configure incoming data for each subscription item except dependent subscription items.
Result
After you complete the configuration, the state of the subscription item and of the subscription changes to Validated.
What to do next
Related topics