What are the Key Capabilities of Informatica MDM MDE?

It provides a Neutral data model.

It is Metadata driven, rules-based with a configurable framework.

Supports Dynamic cell-level survivorship.

Advanced Data Cleansing and Transformations - Enrich the source data by applying various in-built cleanse functions, custom Java cleanse functions, custom stored procedures, and defining user exits.

Provides Out-of-box integration with 3rd party data providers (such as D&B and Acxiom etc.) and identifies common records by matching records against each other within its user interface.

Hierarchy Management - GUI-based functionality enables users to define and configure business rules that decide how data is cleansed, matched, and merged.

Security Access Manager (SAM) - users can create rules to authorize users to view/modify the data and also mask sensitive details if required.

Synchronization - Synchronize with source systems in real-time, near real-time, and batch mode.

Provides unified customer views that can be integrated with business processes (both in real-time, near real-time (or) in batch mode) as browser applications.

What is the possibility to bypass external calls when using the REST API with Informatica MDM?

No, in Informatica Master Data Management (MDM) cannot bypass external calls when calling REST APIs.

If an external call is configured for your system, it will be invoked whenever you use the REST API.

What is the purpose of the Generate Business Entity utility and why is the reference entity name not generated correctly?

The BE-based model of the Data Director application was introduced with MDM v10. Many features have been added to the application over time. A BE-based model is required to use BE-based applications and their APIs (commonly known as BES APIs).

To take advantage of new features and APIs, even SA-based applications must migrate to the BE-based model. Due to the complexity of IDD applications, Informatica MDM provides a utility called Generate Business Entity Service.

When you use this service to convert an SA-based application to a BE-based application, the business entity schema generation results in seven reference entities named A, A2, A3...A7 instead of the correct names such as LUManufacturing will be created.

Generating the business entity schema provides a working BE-based model, but it may not be a one-for-one replacement for SA-based applications as there are multiple scenarios that are handled differently in e360 applications. there is. Therefore, modify the existing BE model and refine it according to your needs.