web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics AX (Archived) Query Retrieval Sequence

Microsoft Dynamics AX (Archived)

Query Retrieval Sequence

(0) Share

Report

Report

Posted on by NR-11010513-0

2

Hi,

Can anyone explain why the join property on a data source is used to determine the sequence in which records are retrieve in an AOT query. This is documented here:

http://msdn.microsoft.com/en-us/library/bb314836.aspx

It seems perverse to me that you would use this property for this purpose. Being unable to use an inner join when you have multiple data sources on the same level would give you adverse results from the query.

Does anyone have any comment?

Cheers,

Nick

*This post is locked for comments

I have the same question (0)

All responses Img

All responses (1)

Answers Img

Answers (0)

Martin Dráb 239,381 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What other solution would you use, taking into account how tables are defined in AX? In SQL, you basically get one new "table", but AX has fixed "classes" describing database tables. When you call QueryRun.next(), data must be fetched somehow to individual tables used in the query().

If you have, let's say, a header and few lines joined together, the first next() fetches the header and the first line, a subsequent next() fetches the second line etc.

If the relation is 1:1, it's all basically the same, QueryRun will just always fetch both records together.

Or what else did you mean?

Was this reply helpful? Yes No

Helpful resources

Quick Links

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1

CP04-islander 39

#2

#3

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans