Closed MotivatedEmployee closed 5 months ago
This is unfortunate because AFAIK (though some NAV veteran might know otherwise) actions have never been actually supported on request pages so we should have blocked them out of the gate when we introduced request pages. Since we cannot now remove them without breaking a lot of things, they're available in AL but they just don't do anything.
This also means we don't want to do any work to support them better in syntax, since the ideal long term goal would be to remove them altogether. So while this is a bug, I don't think it's one that we want to fix.
1. Describe the bug
Even if actions have not been displayed on a report request page for several versions, it is still possible to program them. (It can also be included in historically grown solutions). With a "correctly" developed property 'RunPageView' in a request page on a report, the following message appears in AL version 13.x: Property 'RunPageView' requires an application object reference for the 'RunObject' property.AL (AL0255)
2. To Reproduce
3. Expected behavior Be able to compile with an action with the properties RunObject and RunPageView in a report - requestpage.
4. Actual behavior Can not compile with an action with the properties RunObject and RunPageView in a report - requestpage.
5. Versions: AL Language: v13.0.971907 Visual Studio Code: 1.88.0 (user setup) Business Central: 23.5.16502 / 24.0.16410