Hi,
Thanks for reply
Satish:
Definitely rewriting logic of "CustAgingReport" is not a pice of cake. I don't afraid of choking up AX by external queries - AX chokes up sometimes himself
But seriuosly - direct query to SQL is not so rarely?
Martin:
My enviroment is simple - single language (given), single partition, single company (till now). Table inheritance (getting data from those tables) is known, enums label also (I have dedicated table with all enums data in AX), UTC datatime conversion to local time zone and so on. Things as security are of course unavailable
Especially I wondering about bussines logic: risk of mistakes during reconstruction (ommiting some parameter, which may have impact in the future) or changes of logic eg. AX / processes customization... But performance gain is so huge…
Or maybe rewriting X++ logic to be more, let say, specific / custom without flexibility... It's possible to improve it while we are talking about performance?