Quantcast
Channel: Iulian Cordobin's Groups Activities
Viewing all articles
Browse latest Browse all 1084

Query::insert_Recordset messing the columns orders and throwing error when using complex query

$
0
0

I can't describe very well the problem without creating a long post, and knowing that this might render the question unanswered, here is the short version. I am trying to use a very complex query to use it in a Query::insert_Recordset operation and the AX is messing up the column order and thus is raising errors on issuing the 'insert into select from' t-sql. The query I'm using is not structured with only one datasource per level, but all the FetchMode are 1:1, and only InnerJoins. Switching from my own query to a standard one, I get the same error with GeneralJournal query trying to insert in my own temp table 7 fields from it. The interesting thing is that I move the second datasource sharing the same level to a one datasource per level structure query, it works just fine.

My question: has anyone experienced this? Is there maybe a KB that fixes this (I searched for it before posting the q, but didn't find any hint).

I am pretty sure I am not doing something wrong, so any ideas would be helpful.

Thanks.


Viewing all articles
Browse latest Browse all 1084

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>