What's New > October 2023 > Changed behaviors
  

Changed behaviors

Application Integration includes the following changed behaviors in this release:

Changes in single SQL query response format

In a data access service connector, with the introduction of multiple SQL queries support, the XML response for single and multiple SQL queries begins with the multiDataAccessResponse tag followed by the dataAccessResponse tag.
The following sample snippet shows the new XML response format:
<multiDataAccessResponse>
<dataAccessResponse>
<result statementId="SQL Name 1">
<row>
<table_catalog>activevos</table_catalog>
<table_schema>public</table_schema>
<table_name>aeb4ptaskpa</table_name>
<table_type>BASE TABLE</table_type>
<self_referencing_column_name/>
<reference_generation/>
<user_defined_type_catalog/>
<user_defined_type_schema/>
<user_defined_type_name/>
<is_insertable_into>YES</is_insertable_into>
<is_typed>NO</is_typed>
<commit_action/>
</row>
</result>
</dataAccessResponse>
</multiDataAccessResponse>
Previously, when you made a single SQL query request, the corresponding XML response began with the dataAccessResponse tag.
The following sample snippet shows the previous XML response format:
<dataAccessResponse statementId="SQL Name 1">
<row>
<table_catalog>activevos</table_catalog>
<table_schema>public</table_schema>
<table_name>aeb4ptaskpa</table_name>
<table_type>BASE TABLE</table_type>
<self_referencing_column_name/><reference_generation/>
<user_defined_type_catalog/><user_defined_type_schema/>
<user_defined_type_name/>
<is_insertable_into>YES</is_insertable_into>
<is_typed>NO</is_typed>
<commit_action/>
</row>
</dataAccessResponse>
For more information about single and multiple SQL queries, see Design.

Metadata changes in the response payload of data access service connectors

In a data access service connector, when you request metadata details for a specific app connection using the https:// <Informatica Intelligent Cloud Services URL >/active-bpel/odata/v4/<app connection name>/$metadata URI, the navigation property definition only includes the entity in the navigation property name within the response payload.
The following sample snippet shows the new format of the response payload:
<NavigationProperty Name="SectionODataTest"
Type="Informatica.OData.AppConnectionTestSqlServer1.Models.SectionODataTest">
<ReferentialConstraint Property="sectionid" ReferencedProperty="sectionid"/>
</NavigationProperty>
Previously, the navigation property name also displayed references to the foreign key.
The following sample snippet shows the previous format of the response payload:
<NavigationProperty Name="StudentODataTest_REFERS_TO_SectionODataTest_VIA_FK__StudentOD__secti__67442390"
Type="Informatica.OData.AppConnectionSQLServer1.Models.SectionODataTest">
<ReferentialConstraint Property="sectionid" ReferencedProperty="sectionid"/>
</NavigationProperty>
For more information about the response payload of data access service connectors, see Design.