Describe the bug
RunPageView and SubPageView's where clause suggests fields from the table of the parent page when pressing Ctrl+Space or otherwise invoking the Intellisense auto-complete list. This is obviously wrong, since the page being run probably shows a different child table, and we are filtering its fields, not those of the calling parent page. Thus Intellisense suggests wrong fields, and ones that will give syntax errors once accepted...
To Reproduce
Just have an action or part that use RunPageView or SubPageView respectively, and try creating the where clause and using Ctrl+Space to suggest fields within its ().
Expected behavior
Suggest fields from the child table to be shown by the triggered page/subpage, not parent.
Screenshots
This shows a list page build on the Vendor table, trying to add an action to show Vendor Ledger Entries of type Payment for the current vendor, and getting suggested to filter on fields from the parent Vendor, when they are actually applied to the child Ledger Entry. (Well, I actually got Customer mixed in there, but if anything it just strengthens my point!)
5. Versions:
- AL Language: 6.1.362735
- Business Central: n/a
Describe the bug
RunPageViewandSubPageView'swhereclause suggests fields from the table of the parent page when pressing Ctrl+Space or otherwise invoking the Intellisense auto-complete list. This is obviously wrong, since the page being run probably shows a different child table, and we are filtering its fields, not those of the calling parent page. Thus Intellisense suggests wrong fields, and ones that will give syntax errors once accepted...To Reproduce
Just have an
actionorpartthat useRunPageVieworSubPageViewrespectively, and try creating thewhereclause and using Ctrl+Space to suggest fields within its().Expected behavior
Suggest fields from the child table to be shown by the triggered page/subpage, not parent.
Screenshots
This shows a list page build on the
Vendortable, trying to add anactionto showVendor Ledger Entriesof typePaymentfor the current vendor, and getting suggested to filter on fields from the parentVendor, when they are actually applied to the childLedger Entry. (Well, I actually gotCustomermixed in there, but if anything it just strengthens my point!)5. Versions: