Dynamics 365 FO / AX - thoughts on application development and customizations

This is an old blog entry from my old blog. Today I solved a problem, that has long puzzled me. From Axapta 3.0 (or was it 2.5 can't quite remember) it became best pratice to wrap reports in runbase-report classes. For a long time it has irritated me, that if you called your report class from something else than the menu, you were having trouble overriding syslastvalue, without clearing all saved last value completely. Example: You have a report called from a runbasereport class.For the class you naturally have a output menuitem, that is attached to the menu. So when you call this report, and make selections in the ranges of the query of the report, they are shown in the report dialog, and saved, so that the next time you call your report, the last used selections is being restored for you in the dialog for reuse. However sometime you experience, that the report can be called from BOTH the menu and somewhere else like a form. When you call the report from a form, it is customary to