What can you do?
AIF supports a Microsoft Dynamics AX installation that has multiple partitions. The new data partitioning feature affects the way data is accessed by service operations in Microsoft Dynamics AX. Each service request must contain the information to identify a specific partition. If you do not specify a partition in the call context or message header XML, AIF uses the default partition for the calling user.
The administration of AIF is not per-partition. That is, the administration forms provide a view of the status of the service operation infrastructure that includes inbound and outbound integration ports, the message history, and the exception log, for all partitions at the same time.
The call context, the schema for the message header, and the administration form for inbound ports have changed to enable you to restrict service requests to a specific partition.
Note:
In Microsoft Dynamics AX 2012 R2, AIF includes support for optional replacement fields for a surrogate foreign key that has multiple replacement fields. In other words, a replacement field is optional if the referring surrogate foreign key field is specified as non-mandatory on the table.
In previous versions of Microsoft Dynamics AX, AIF considered all surrogate foreign key replacement fields as mandatory. For outbound transfers, this meant that previous versions of Dynamics AX serialized each field when sending Axd documents. Therefore, in external clients written to use outbound document services in previous versions of Microsoft Dynamics AX, fields that were previously mandatory are now optional, and may be missing from the XML message.
My above blog is based on Microsoft's Official information.
I
hope this blog about 'Microsoft Dynamics AX 2012 R2 - What's New for Developers in Feature area of Services and Application Integration Framework (AIF)' was
informative.
Please feel free to leave your
comments.
No comments:
Post a Comment