Dear Friends
Those who are familiar with OData may notice that the OData query service has a few limitations. It's important to know these and not make assumptions so that you don't run into any surprises. The limitations are as follows:
• No JSON support: The OData protocol supports Atom as well as JSON, but Microsoft Dynamics AX 2012 only supports Atom.
• No create, update, or delete: With OData, you can also modify data instead of only reading it, but this feature is not supported in Microsoft Dynamics AX 2012.
• No support for query options: OData supports query options that allow you to, for example, select only the top five records, select only a specific entry, or sort the feed; however, this feature is not supported in Microsoft Dynamics AX 2012 and using it will result in an error.
• No support for queries with fetch mode 1:n: Using a query that has a data source which has its fetch mode set to 1:n will result in an error in the event log for the Feature Pack release and a warning for the R2 release. The latter will automatically convert the 1:n fetch mode to 1:1, which is the only fetch
mode that is supported.
• No support for views: Queries that use views are not supported, and using a view will result in an error.
Happy DAXing.... :)
Those who are familiar with OData may notice that the OData query service has a few limitations. It's important to know these and not make assumptions so that you don't run into any surprises. The limitations are as follows:
• No JSON support: The OData protocol supports Atom as well as JSON, but Microsoft Dynamics AX 2012 only supports Atom.
• No create, update, or delete: With OData, you can also modify data instead of only reading it, but this feature is not supported in Microsoft Dynamics AX 2012.
• No support for query options: OData supports query options that allow you to, for example, select only the top five records, select only a specific entry, or sort the feed; however, this feature is not supported in Microsoft Dynamics AX 2012 and using it will result in an error.
• No support for queries with fetch mode 1:n: Using a query that has a data source which has its fetch mode set to 1:n will result in an error in the event log for the Feature Pack release and a warning for the R2 release. The latter will automatically convert the 1:n fetch mode to 1:1, which is the only fetch
mode that is supported.
• No support for views: Queries that use views are not supported, and using a view will result in an error.
Happy DAXing.... :)
