25
Hello,
I would like to make a suggestion on this, from the first version of Query that rolled out for NAV i hasn't changed so much the query. I know that the idea of the querys is to only read data from tables. But due that it's the fastest way to read tons of registers of data, is a good choice when we want to read that quantity of information.
I see that there are a lot of limitations, and it would be really nice to add the possibility of adding functions (for example to store rows in a table buffer, like an xmlport), settableview with a filtered rec (to give the choice of changecompany or whatever).
Thanks for your effort, you're making a great work. My congratulations.
Best regards,
Jamal Bakach
I would like to make a suggestion on this, from the first version of Query that rolled out for NAV i hasn't changed so much the query. I know that the idea of the querys is to only read data from tables. But due that it's the fastest way to read tons of registers of data, is a good choice when we want to read that quantity of information.
I see that there are a lot of limitations, and it would be really nice to add the possibility of adding functions (for example to store rows in a table buffer, like an xmlport), settableview with a filtered rec (to give the choice of changecompany or whatever).
Thanks for your effort, you're making a great work. My congratulations.
Best regards,
Jamal Bakach
STATUS DETAILS
Needs Votes
