The best way to kill Business Central performance with a single line of code

What does InDataset do?
Can you explain it deeoer?

Thank you ever so much

[chriswatson]

Thanks for your 'Worst Practice' tips. Of course, I would never do anything like that...

[senditjason]

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.

[carstenhansen]

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?

[TheJulietteCharlie]

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.

[realeques]

3:58 i'd say most pages are not edible, great work though 😂