Release Notes > Business 360 Console > Known issues

Known issues

The following table describes the Informatica Intelligent Cloud Services Business 360 Console known issues. The (<release>) value in each issue description indicates the release in which the issue was reported.
When you add a title for a panel that contains a Dynamic Fields component, the Dynamic Fields section doesn't appear on the business applications. The issue occurs when the Dynamic Fields component doesn't contain any root fields.
Workaround: Remove the title of the panel and add a title to the Dynamic Fields component. Alternatively, add at least one root field to the Dynamic Fields component.
When you purge records that belong to a specific business entity, the purge might take a long time and fail. Purge might fail due to a large volume of business entity records, relationship records, and historical data.
(April 2024)
When you enable picklist fields in a business entity as facetable and search records through the Search REST API, the search response doesn't display the code field. However, if you enable the picklist fields as searchable or searchable and facetable, the search response displays the name and code fields.
(April 2024)
After you update the search configuration, if users run a saved search that contains fields that are no longer searchable, they get the following error:
Search API service failed.
Workaround: Users must remove the non-searchable fields from their saved searches.
(April 2024)
When you configure an advanced rule association and add a value to any one of the input fields, Business 360 Console doesn't save the rule association.
(April 2024)
In Operational Insights, when you view the ingress job metrics, the number of imported records appears inconsistent between the job instance and performance details panels.
(April 2024)
When you add a record-level data access rule for a custom user role with approval privileges, the user can't view the title of the workflow task in the business application.
Workaround: Modify the record-level data access rule to an attribute-level data access rule, or delete the data access rule.
(April 2024)
When you run an ingress job, Business 360 Console ignores the values for the fields named as Message Type even though the job succeeds. This issue occurs becauseBusiness 360 Console internally uses the MessageType field to store the operation type that you specify in the Cloud Data Integration mapping.
Workaround: Ensure that you don't use Message Type as a field name.
(April 2024)
When an egress job fails, an incorrect error message appears instead of displaying the exact reason for the failure.
(April 2024)
If a relationship attribute contains a decimal value with a precision of more than 34, the digits after the 34th digit are replaced with zeroes.
(April 2024)
When you set conditions for business entity attributes in a data access rule, the Attribute field incorrectly displays the system fields that are enabled as searchable.
Workaround: Ignore the system fields that are listed in the Attribute field and don't create conditions based on the system fields.
(April 2024)
When you configure the properties of business entity fields, you can't view all the validation messages because the validation panel doesn't have a scroll bar.
(April 2024)
If you create a business entity, add advanced rule associations for the fields in the business entity, and then save the business entity, Business 360 Console doesn't display the mapped business entity fields in the Output Fields section.
This issue also occurs when you import the same business entity from the source to the target organization.
Workaround: Ensure that you save the business entity before you add advanced rule associations to the business entity fields.
(April 2024)
When users unmerge records, the address values of the unmerged records aren't enriched even though the address fields have DaaS rule associations for real-time address verification configured.
This issue occurs when the preview feature for validation errors is enabled.
(April 2024)
When you import or export data that contains date fields to and from MDM SaaS, the system decrements the dates prior to 1582 by 10 days.
(February 2024)
When a source primary key in a REST API request URL contains the caret character (^), the API request fails.
(April 2024)
When you match records that include records from a distinct source system, the match process might not generate few record pairs.
(February 2024)
Users with the Product 360 Read Only and Supplier 360 Read Only user roles can't view the Hierarchy tab of a record even though they can view the Hierarchies page in a business application.
Workaround: Create a custom user role with read-only privilege for the Hierarchy Component on the Security page and assign the custom user role to users.
(February 2024)
When you download the match output report of a match and merge job, the record pairs count in the report might not be the same as the count that appears on Business 360 Console. The issue occurs if another match and merge job runs after the match and merge job for which you downloaded the report.
Workaround: To view the correct match report output, download the report immediately after the job completes.
(February 2024)
When you export hierarchies and relationships that belong to a specific source system by using Business FEP Connector, the egress job exports hierarchies and relationships from all the source systems.
(November 2023)
On the Explore page, when you view the dependencies of a business entity and open a job definition from the Used By tab, the job definition page doesn't display the information correctly.
Workaround: To view the correct information, open the job definition from the Explore page.
(November 2023)
When you import a predefined business entity to an organization from where you exported the business entity and provide a custom project path, the predefined Data Quality assets are saved in both the default and custom projects.
Workaround: To avoid duplication of the predefined Data Quality assets, don't enter the custom project path when you import a predefined business entity.
(November 2023)
When you run an ingress job, the job validates all the fields in a field group even if you don't map the fields configured with data quality rule associations.
(November 2023)
When you import a searchable hierarchy into an organization, the process hierarchies job doesn't automatically run.
Workaround: Run the process hierarchies job to index the records of the searchable hierarchy.
(October 2023)
When you apply the changes to the source ranking of a field, the ranking is automatically saved with a new label.
(October 2023)
When you apply the changes to the source ranking of a field, two labels appear for the same source ranking.
(October 2023)
When a business entity doesn't have a self-referential relationship with itself, the dynamic field definitions of a parent record can't be enabled for inheritance in business applications.
(October 2023)
If business entities have only numeric fields, the search operation using the search box might fail in business applications. The search operation fails when users enter a search value other than integers in the search box.
(October 2023)
When you add an integrity check based on a business entity attribute, business entity record fields appear as attribute options in the Add Integrity Check dialog box. The issue occurs if there are at least three business entities and each business entity has a business entity record field relationship with another business entity.
(October 2023)
In Operational Insights, when you filter the ingress job metrics based on the hierarchy or relationship asset type, the metrics don't appear.
(September 2023)
When you filter by job types on the My Jobs page, the following issues occur:
  • - The list of job types includes duplicate entries.
  • - Some job type names aren't user-friendly and appear as internal template names.
(August 2023)
Users with custom user roles can't delete business events.
In Operational Insights, the usage summary for MDM SaaS doesn't refresh.
Workaround: After you initiate the summary refresh, wait for the estimated refresh time. You can then refresh the Overview page to view the latest usage summary.
(August 2023)
The data access rules with conditions on relationship attributes and related business entity attributes don't work as expected. These rules incorrectly authorize users to view records when conditions apply to multiple field groups or multiple related records.
(August 2023)
If different state codes have the same values, the real-time address verification doesn't validate and populate values for the state fields because Reference 360 stores unique values for the code fields.
(August 2023)
When you run an ingress job to load incremental data, the job might take longer to complete than the initial load for the same load volume.
(July 2023)
When a dependent picklist field in a record contains a null or an invalid value, you can't save any changes to the record. On the Record Details page, the Submit button appears disabled.
Workaround: On the Record Details page, select a valid value for the dependent picklist field and submit the changes.
(July 2023)
If data access rule names contain special characters or characters of languages other than English, you can't open the rules from the user role details page or the rules list page.
(July 2023)
When you view the details of MDM SaaS jobs in the Operational Insights service, the data is inconsistent between the job instance and performance details panels.
(July 2023)
When you view the performance details of MDM SaaS jobs in the Operational Insights service, the time taken for the jobs to complete appears inconsistent. The inconsistency appears on the job instance and performance details panels. Also, the performance details panel displays the end date and time of jobs that are running.
(July 2023)
When you use the Create Master Record API to create a record without specifying required field values, the record is created without validation errors.
After users delete a value of a field in a field group that has uniqueness criteria configured, users can continue to see a value for the field. This issue occurs when you have another duplicate entry for the field group.
(June 2023)
If you search for job instances after applying a filter on the My Jobs page, the search request incorrectly applies to all job instances. Also, you can't use job statuses as search criteria for finding job schedules.
(May 2023)
You can't configure data access rules or revoke read privilege to restrict access to record names for custom user roles. The record name appears in the title and description of tasks listed in the workflow inbox. The issue occurs if you configure the record name as the title and description for business events.
(May 2023)
When you import a business entity that has DaaS rule associations and integrity checks along with its dependent objects into another organization, the import process fails. The issue occurs when you override the existing assets during the import process.
Workaround: Import the business entity, and then the dependent objects without overriding any existing assets.
(May 2023)
After you purge records that belong to a specific business entity, the metrics for the purge matched record pairs step don't include the number of match pairs collected.
(April 2023)
When you unmerge records with relationship attributes that are updated after the records are merged, the updated values are lost. The unmerge operation causes the attributes to return to the default values that existed before the merge, or changes the attributes to have no values.
(April 2023)
When you use the Source Record API to retrieve a source record, the GET request can't contain the pipe (|) symbol encoded as part of the URI. It fails with a bad request error.
(April 2023)
When you download translation files, some translations in the files might not apply to your business applications.
Workaround: Ignore the translations that aren't applicable.
(February 2023)
If you create data access rules for relationship or related business entity, the number of records for facetable fields is incorrect in the filters panel of the search results page for custom user roles.
(February 2023)
If a data access rule has conditions on a field that isn't searchable or conditions on relationship attributes or related business entity attributes, the search requests don't work as expected for custom user roles. If more than 10000 records exist for the business entity, when a user with the custom user role searches for records, the search results page doesn't retrieve matching records.
(February 2023)
When you try to delete a custom asset, the asset doesn't show up on the Explore page, but doesn't get removed completely.
Workaround: To ensure that you completely delete a custom asset, contact Informatica Global Customer Support.
(February 2023)
You can't change the predefined translations for the Related Records, General Information, and Select Date sections.
(February 2023)
When you run an ingress job to import data with integer fields, and if the value of an integer field exceeds the maximum limit of 2147483647, the ingress job fails.
Workaround: Use text fields instead of integer fields if the value of an integer field exceeds the maximum limit and run the job again.
(January 2023)
When you configure a page with the Header 2 template, if the values of breadcrumb, line 1, or line 2 fields are long, the values might wrap or overlap.
(December 2022)
When an upgrade job is successful, a notification appears that indicates the job has failed.
Workaround: Ignore the notification. The My Jobs page shows that the job is successful.
(December 2022)
In an organization that uses real-time address enrichment, when the users edit any address on the Workflow Inbox page, the business application doesn't enrich the address of the records in real time.
(December 2022)
When you run egress jobs to export large number of hierarchy records, if the hierarchy data has duplicate relationships, the number of exported records varies in each run of the egress job.
(December 2022)
When you add an exact match field in a declarative rule, if you click the Field Name picklist, the previously added exact match field incorrectly appears.
Workaround: After you add an exact match field, click outside the Add Declarative Rule dialog box.
(December 2022)
On the My Jobs page, the status of completed egress jobs might incorrectly appear as running.
(November 2022)
You can't export a large number of records if the size of each record exceeds 2.5 MB for more than 1000 records in the data that you export. The egress job might fail with an out-of-memory error.
(November 2022)
When you export a report from one organization and import the report to another organization, the imported report doesn't appear on the Reports page in Customer 360.
Workaround. Export the Report Set asset from one organization and import the Report Set asset to another organization for the reports to appear in Customer 360.
(September 2022)
If you have sub-organizations in your environment, you can see the Support Access tab on the Global Settings page of your sub-organization. The tab shouldn't appear.
(September 2022)
When Informatica Global Customer Support users access your organization after you grant access, the Add, Delete, and Edit buttons appear enabled. However, the users can't save changes to the assets.
(September 2022)
When you export data from a business entity that contains nested field groups, you cannot identify the parent field group for each child field group in the exported data.
Workaround: To identify the parent field group, manually refer to multiple files in the exported data and then associate the parentId value of the child field group with the sourcePkey value of the parent field group.
(August 2022)
When you enable source control in Administrator, the following processes might fail:
  • - Upgrading business applications
  • - Importing and exporting assets
(August 2022)
You aren't warned when you manually merge records that belong to different populations.
(June 2022)
Even though users with custom user roles aren't assigned the Business360ProcessExecutor role in Administrator, these users can access the option to create hierarchies in the business applications. When these users try to create a hierarchy, the following error occurs:
Cannot create the hierarchy <hierarchy name>.
Workaround: To enable users with a custom user role to create hierarchies, assign the privileges for creating hierarchies on the Security page and the Business360ProcessExecutor role in Administrator.
(June 2022)
When you ingress records that belong to populations that aren't supported, such as aml or ofac, the data loads into the data store, but match tokenization fails. Records with invalid population names do not load.
(June 2022)
For a custom user role, the read and update privileges that you assign for a hierarchy model and its associated relationships and business entities do not work as expected. The "Authorization cannot be granted" error appears incorrectly when a user with the custom user role performs the following tasks:
  • - When the user deletes the attribute value of a relationship within the hierarchy.
  • - When the user with workflow approver privilege opens a hierarchy task on the Workflow Inbox page and adds an attribute value for a relationship within the hierarchy.
(May 2022)
For a custom user role, the read privileges that you assign for a hierarchy and its associated relationships and business entities do not work as expected. When a user with the custom user role tries to view the hierarchy record in the business application at a specific point in time, the user gets the following errors:
Authorization cannot be granted.
Cannot find history data for this hierarchy at given point in time.
(May 2022)
If you enable the delete privilege for a business entity on the Security page, the delete and cut icons for the custom fields are not enabled on the Attributes tab of that business entity as expected.
(April 2022)
If you import an egress job that exports hierarchy or relationship data to a target organization, the import job fails with the following error:
Metadata object with id: <hierarchy name>/<relationship name> was not found!
Workaround: Create an egress job in the target organization and add the associated taskflow that exports hierarchy or relationship data.
(March 2022)
When you run an ingress job to import more than 300,000 records into a data model that contains more than 20 field groups, the ingress job fails.
Workaround: Use a taskflow that contains mappings with individual source object for each field group.
(February 2022)
When you define a business entity, you might not be able to drag and drop fields to the canvas.
Workaround: Collapse and expand the field category and try again.
(December 2020)
After you select a taskflow in an egress job, the Record Type and Source System columns do not appear as lists.
Workaround: Click the Record Type and Source System column values to view them as lists and select the required option.
(February 2022)
On the My Jobs page, the search box on the Job Instances tab fails to retrieve the job instances if you use a job type value as the search text. The search box on the Job Schedules tab fails to retrieve the job schedules if you use a status as the search text.
Workaround: To find job instances and job schedules based on the job type or status values, use the filter option.
(February 2022)
The Merge API can't merge master records that have more than 1000 source records.
(February 2022)
The search box in a custom page does not work as expected when you configure the following user interface elements:
  • - Page header fields
  • - Education field group
  • - Display fields of the business entity
(December 2021)
When you add a taskflow to an export job, the complete names of source systems might not appear due to space constraints.
Workaround: Hover over a source system name to view its complete name.
(December 2021)
When you create a user-triggered event for a hierarchy that requires a workflow and then create a relationship between two business entities, the workflow task does not trigger.
(November 2021)
You cannot delete a custom business entity field that is a part of file import field mapping.
(September 2021)
The users can view the historical data of fields that are not part of the page layout.
(September 2021)
When you open the Customer 360 business application and try to add a custom page for a business entity, the Select a page dialog box does not display the custom page that you created for the business entity.
Workaround: Close the Customer 360 business application and open it again.
(September 2021)
When you create a custom page with a tab title or component title starting with $c360., the tab title and the component title appear different in Customer 360.
(September 2021)
A custom user role with the read privilege to access the Match tab of a business entity can perform edit and delete tasks on the Match tab.
(August 2021)
The attribute names that you can use in the REST API requests are case sensitive.
(August 2021)
The Date and Time fields that you can use in the REST API requests support only the Unix epoch time format.
(August 2021)
For a custom user role, if you assign the create and read privileges to the attributes of a predefined business entity, the create privilege does not work as expected. When the user creates custom fields and saves the business entity, the following error occurs:
Metadata authorization error.
Workaround: Assign the update privilege for the business entity attributes in addition to the create and read privileges.
(August 2021)
When you run an ingress job that processes records with multiple value fields, and both updates and deletes are part of the process, the process deletes records but ignores updates to the records.
(August 2021)
You can't delete custom smart fields even when they don't contain dependencies.
(August 2021)
You can't delete fields and field groups of custom business entities that were previously used in custom pages.
(August 2021)
When you create a business entity field with display name ending with colon (:), the field label does not appear in Customer 360.
(July 2021)
When you render the Alternate Names field group as a card in a custom page, the page validation does not work as expected.
(July 2021)
When you configure a custom page, if you add a custom field group that does not allow multiple instances, the field group do not work as expected in Customer 360.
(December 2020)
If you configure fields to allow multiple values, the fields do not appear in Customer 360.
Workaround: Delete the multiple value fields, and then create the fields again as single value fields.
(December 2020)
When you manually stop or pause a running job, the job status might not update in the My Jobs page.
(December 2020)
In the Explore page, you cannot use the following Action menu items to perform actions on the Business 360 application assets:
  • - Properties
  • - Copy To
  • - Move To
  • - Export
  • - Show Dependencies
  • - Permissions
  • - Delete
(December 2020)
If you edit the candidate selection criteria, the changes are effective only for new records. The criteria doesn't apply to the existing records.
(December 2020)