Closed spesotskiy closed 5 months ago
By the way, the line number that is shown in the call stack :
does not correspond with the line numbers in code coverage. This is the number of the line counting from the start of the function/trigger. So, I need to find the number of the function line first, then add 37, to get the line number in the source file and in code coverage table. Also, such a relative number does not help to find which of the overloaded functions is called, as there are no params in the call stack and relative line number cannot help at all. Just put absolute line numbers like in Code Coverage data.
So, the expected behavior section should be:
Code Coverage
table. Not Trigger OnValidate()
, but Bill-to Customer No. - OnValidate"(Trigger)
Call Stack
message.Sorry Stan. This is a runtime issue.
If you can trigger a Request For Hotfix I am sure it will be considered.
1. Describe the bug AL Code Coverage page shows the field triggers without the field name, so it is not possible to find code related to a certain field without looking through AL source file.
2. To Reproduce Steps to reproduce the behavior:
AL Code Coverage (130460, Worksheet)
, SetObject Id Filter
to36
Page 130460
: Start the coverageSales Order
and put any customer code toSell-to Customer No.
fieldPage 130460
: Stop the coverage; Refresh.Sell-to Customer No. - OnValidate()
line to see if it is all covered.3. Expected behavior The code coverage line for a field trigger must include the field name, so you can recognize triggers easily., like it is in the standard error call stack string, e.g.
4. Actual behavior All field triggers are listed without field names:
5. Versions: