Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.4 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Integrating Data as a Service
  15. Configuring External Calls
  16. Designing the Data Director User Interface
  17. Localizing Data Director
  18. Appendix A: Provisioning Tool Frequently Asked Questions

Provisioning Tool Guide

Provisioning Tool Guide

Back Next

Record Details

Record Details

The Record Details component is a primary component that displays data in a business entity record. Add the Record Details component to a custom Business Entity view layout or review task layout.
The Record Details component appears in the Layout Designer after a business entity model is created in the Modeling page. When you design a layout, you can configure the Record Details component to display the information you want, such as telephone numbers, emails, and addresses. If you display multiple child records that contain large amounts of information, you might want to enable the business entity menu to help users navigate among the child records.
The following image shows a sample Record Details component with the business entity menu in
Data Director
:
The sample Record Details component contains the information for James Smith and a vertical menu.

Best Practices for Record Details Component

Informatica recommends that you use only one Record Details component in a Business Entity view layout.
However, if you must use multiple Record Details components in a Business Entity view layout, consider the following implications:
  • If the set of fields for which you configure a validation or data cleansing rule are split across Record Details components, the validation and cleanse operations fail. Ensure that you configure validation and data cleansing rules for a set of fields that are within a single component.
  • Users need to save changes to fields within one component before making changes to fields in another component. Otherwise, changes made to the fields in the component will be lost.
0 COMMENTS
We’d like to hear from you!