AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 04.10.2007, 11:20   #1  
Blog bot is offline
Blog bot
Участник
 
25,459 / 846 (79) +++++++
Регистрация: 28.10.2006
Inside Dynamics AX 4.0: The XML Structure
Источник: http://feeds.feedburner.com/~r/Insid...structure.html
==============

The primary goal for the Dynamics AX XML document feature was a reduction in implementation time for new XML documents. Because most systems integrating with Dynamics AX need mapping columns regardless of the schema, the product team decided to implement the Dynamics AX internal schema as the API. This way, only one mapping per integration endpoint is needed, and most Dynamics AX developers are already familiar with the internal schema.

It was clear that this should be expressed using AOT queries. The data sources for the AOT query directly associate with tables, and these tables carry fields which in the XML translate into properties. Benefiting from the extended data type definitions in the AOT, the XML schema definition (XSD) can be constrained using the available metadata describing data type, field sizes, and so on.

The widely adopted approach in the XML community regarding properties appearing in a fixed sort order in the documents is supported by the query structure, in which tables are addressed in the order of appearance in the query. The XML document framework automatically addresses the fields in alphabetical order; individual documents therefore require no manual development. Note that if the same table will be referenced in several nodes in the query, XML schema restrictions require that the name be unique. The table fields, when referenced in the XML, are referenced with their field names from the table, but the table names are the name under which they are identified on the query.

The limitations are that only one root table per query is allowed, and the unique entity key of an XML document can be associated with this root table. When constructing the queries, you should outer-join the child data sources to uphold 1:n relationships. If 1:1 relationships are to be enforced, you should choose an inner join.


In below image illustrates the mapping between the query in the AOT, which is referenced by the Axd class, and the XML document structure.



Correlation between the AOT query and the XML document structure
http://insidedynamicsax.blogspot.com/
</img> </img> </img> </img> </img>


Источник: http://feeds.feedburner.com/~r/Insid...structure.html
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
axStart: Microsoft Dynamics AX 2009 Hot Topics Web Seminar Series Blog bot DAX Blogs 0 06.08.2008 12:05
Inside Dynamics AX 4.0: XML Document Integration Blog bot DAX Blogs 0 04.10.2007 11:20
Inside Dynamics AX 4.0: Working with the .NET Business Connector Blog bot DAX Blogs 0 04.10.2007 05:15
Inside Dynamics AX 4.0: Usage Scenarios Blog bot DAX Blogs 0 04.10.2007 05:15
Inside Dynamics AX 4.0: Inside the Business Connector Blog bot DAX Blogs 0 04.10.2007 05:15
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 02:21.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.