Why do you need this change?
We are developing a report extension on Report 20 "Calc. and Post VAT Settlement" that needs to enforce a business rule: prevent posting the VAT Settlement when an Activity Code Filter is set.
Currently, the ActivityCodeFilter variable is declared under var (private scope). From our report extension, we are unable to access the ActivityCodeFilter variable because it is declared as private and is not passed as a parameter in any of the existing integration events exposed by the report.
This forces us to maintain a separate boolean flag that tracks whether the user has interacted with the field ΓÇö but this approach is unreliable because:
- We cannot detect if the user clears the filter after setting it (the flag stays true, causing false positives).
- If the report is invoked without the request page, we have no way to verify the filter value server-side.
Making ActivityCodeFilter a protected var would allow us to read the actual filter value directly in our report extension, enabling a reliable and accurate validation.
Describe the request
We would need the ActivityCodeFilter variable in Report 20 "Calc. and Post VAT Settlement" to be moved to protected var in order to make it accessible from report extensions.
Current declaration:
var
...
CountryRegionFilter: Text;
ActivityCodeFilter: Text; // OLDRequested change:
protected var
GLAccSettle: Record "G/L Account";
PostSettlement: Boolean;
EntrdStartDate: Date;
EndDateReq: Date;
PostingDate: Date;
ActivityCodeFilter: Text; // NEWInternal work item: AB#635591
Why do you need this change?
We are developing a report extension on Report 20 "Calc. and Post VAT Settlement" that needs to enforce a business rule: prevent posting the VAT Settlement when an Activity Code Filter is set.
Currently, the ActivityCodeFilter variable is declared under var (private scope). From our report extension, we are unable to access the ActivityCodeFilter variable because it is declared as private and is not passed as a parameter in any of the existing integration events exposed by the report.
This forces us to maintain a separate boolean flag that tracks whether the user has interacted with the field ΓÇö but this approach is unreliable because:
Making ActivityCodeFilter a protected var would allow us to read the actual filter value directly in our report extension, enabling a reliable and accurate validation.
Describe the request
We would need the ActivityCodeFilter variable in Report 20 "Calc. and Post VAT Settlement" to be moved to protected var in order to make it accessible from report extensions.
Current declaration:
Requested change:
Internal work item: AB#635591