I would say it's pretty rare to modify records as you're retrieving to a List Page. If I really had to this, then I would use a temporary copy of the record and populate the field, then reference that temp table.field in the column; thus keeping it all in memory. On page.close you could write to the real table from temp table.
3 года назад+2
What does InDataset do? Can you explain it deeoer? Thank you ever so much
Sorry, I had a speech deficit as a kid and English is my second language, still learning every day, trying very hard not to make these mistakes, sorry again.
@Erik Hougaard i'm just messing with you , i started working full time as a developer this month and we are migrating from navision 2009 to business central , i don't know what i would do without your videos 😁
Modify on each or many scrolled lines in a List? I‘d never have done this, really. Buffering in a temp table behind the scenes must be done properly and could lead to even more problems. The buffer could grow fast and on saving the results on closing the page could take time as well. Don’t mess with too much UI features and do not mess with database transactions. The NAV/BC are kind of weird. But until you use COMMIT; carefully if justified, then it’s better than handle it properly by your own. What is still unclear for me is how to use OnAfterGetCurrentRecord instead of the OnAfterGetRecord.
Use cases: - You need sorting and filter (I would use TMP table) - You need to log that the user have seen the record (use TMP table like classic report logging). Maybe you can recommend something else?
i guess you mean if an user open a card page because in a list i think it´s difficult to know what record the user has seen, in card page i would log on OnOpenPage.
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
I would say it's pretty rare to modify records as you're retrieving to a List Page. If I really had to this, then I would use a temporary copy of the record and populate the field, then reference that temp table.field in the column; thus keeping it all in memory. On page.close you could write to the real table from temp table.
What does InDataset do?
Can you explain it deeoer?
Thank you ever so much
Will put it on the list :)
@@Hougaard this would be awesome. :)
3:58 i'd say most pages are not edible , great work though 😂
Sorry, I had a speech deficit as a kid and English is my second language, still learning every day, trying very hard not to make these mistakes, sorry again.
@Erik Hougaard i'm just messing with you , i started working full time as a developer this month and we are migrating from navision 2009 to business central , i don't know what i would do without your videos 😁
Modify on each or many scrolled lines in a List? I‘d never have done this, really. Buffering in a temp table behind the scenes must be done properly and could lead to even more problems. The buffer could grow fast and on saving the results on closing the page could take time as well.
Don’t mess with too much UI features and do not mess with database transactions. The NAV/BC are kind of weird. But until you use COMMIT; carefully if justified, then it’s better than handle it properly by your own.
What is still unclear for me is how to use OnAfterGetCurrentRecord instead of the OnAfterGetRecord.
Use cases:
- You need sorting and filter (I would use TMP table)
- You need to log that the user have seen the record (use TMP table like classic report logging). Maybe you can recommend something else?
i guess you mean if an user open a card page because in a list i think it´s difficult to know what record the user has seen, in card page i would log on OnOpenPage.
Thanks for your 'Worst Practice' tips. Of course, I would never do anything like that...
Of course not :)
Thanks!