Validate foundation data sync subscription items
Configure the sample data received from the provider to validate a foundation data sync (FDS) subscription item.
Before you begin
Role required: admin
About this task
After you create an FDS offering request, the provider acknowledges the request and sends you a sample payload. This payload helps you understand the structure and type of data you’ll receive.
After the provider sends the sample, a subscription is generated for each offering in the FDS offering request and each subscription contains a subscription item for each table the provider is sharing. You must configure the incoming sample data to validate the FDS subscription items.
Procedure
Navigate to All > Service Exchange Consumer > FDS Requests.
Select the request.
From the Foundation Data Consumer Subscriptions related list, open the consumer 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.
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), CMDB with Maintain sysID enabled by the provider, 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.
Note: Since FDS provides display values for reference fields, if you want to use reference data, you must create a table lookup 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.