Changed behavior

A Salesforce organization can now be mapped to only one IDMC organization at a time during synchronization from Salesforce. When you synchronize a Salesforce organization with a new IDMC organization, Application Integration automatically removes the Salesforce organization link from the IDMC organization that it was previously mapped to, so that only the most recent mapping remains active. This change is applied automatically during synchronization. No action is required on your part.

Previously, Application Integration retained the earlier mapping, which allowed a single Salesforce organization to remain mapped to multiple IDMC organizations at the same time.

For more information, see Design.

You can generate a unique process object when you create a service connector from a Web Services Description Language (WSDL) or XML Schema Definition (XSD) file that contains repeated complex type names. This change ensures that the process object mapping accurately captures and preserves action-specific request and response fields.

Previously, when you created a service connector by importing a WSDL or XSD file that contained repeated complex type names, Application Integration generated only a single process object based on the first occurrence of that metadata name. It mapped subsequent actions that used the same complex type name to this initial process object, ignoring the unique child elements and metadata structures defined for the other actions.

For more information, see Design.

Google BigQuery V2 connections support only the Simple and Hybrid connection modes. The Complex connection mode is no longer available in the Connection Mode field for Google BigQuery V2 connections.

Previously, you could set the connection mode to Complex. However, the Complex mode returned all the data as a single string field and did not support query-based use cases in Application Integration.

If you have existing Google BigQuery V2 connections configured in the Complex mode, reconfigure them to use the Simple or Hybrid mode.

For more information, see Google BigQuery V2 Connector Guide.

You can now run OData API requests and Informatica Process Designer process requests against Microsoft Fabric databases without pagination failures. To enable this behavior, add the aeEnableDefaultPagination=true parameter to your Microsoft Fabric JDBC connection URL. After you add the parameter, OData API requests and Process Designer processes can successfully retrieve paginated results from Microsoft Fabric databases.

Previously, requests with $skip=0 or incomplete pagination parameters returned errors because Microsoft Fabric does not support the T-SQL SET ROWCOUNT statement.

When you download an Application Integration usage report in Operational Insights, the time range between the start and end dates can't exceed 13 months.

Previously, a request for a range longer than 13 months returned a success response with no data, which made it unclear whether the range exceeded the limit or the period genuinely contained no data. Now, a request for a range longer than 13 months returns an error that explains the limit, so you can tell that you need to shorten the date range instead of assuming that no data exists for the period.

For more information, see Operational Insights.

To enable replication upgrade of the Process Server PostgreSQL database for a Secure Agent, access the following directory:

Then, run the following command:

Previously, to enable replication upgrade of the Process Server PostgreSQL database for a Secure Agent, you added a custom property for the Secure Agent.

For more information, see Secure Agent Services.

A data access service (DAS) connector caches schema metadata for improved performance. The connector now caches the list of tables and views for a schema after the first OData request, and reuses the cached list for subsequent requests.

Previously, the connector retrieved this list from the database on every OData request.

If you change the database structure, you must republish the connector to refresh the cached list and reflect the changes.

For more information, see Design.