You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are extending Page 7002 "Sales Prices" using a page extension and have a requirement to reuse the existing filtering logic.
The page internally uses the following global variables:
StartingDateFilter
CurrencyCodeFilter
These variables are essential for filtering sales price data and are already used within the standard application logic. However, they are currently not accessible from page extensions, which limits the ability to create consistent and reusable customizations.
When implementing custom actions or logic in a page extension of page 7002, we cannot: Access the current values of StartingDateFilter and CurrencyCodeFilter
Reuse standard filtering logic already applied by the page
Ensure consistency between standard filtering behavior and custom functionality
As a result, we are forced to: Duplicate filtering logic manually
Maintain separate custom variables
Risk inconsistencies with future Microsoft updates
This limitation leads to: Reduced extensibility of standard pages
Additional development and maintenance effort
Increased risk of discrepancies between standard and custom behavior
Less upgrade-safe customizations
On Page 7002 "Sales Prices", the procedure GetRecFilters() is currently defined as local, which prevents it from being accessed or reused in page extensions.
This procedure contains important standard logic responsible for: Processing record filters
Calling internal filtering logic (UpdateBasicRecFilters)
Assigning StartingDateFilter based on the current page filters
Because GetRecFilters() is local:
Extensions cannot invoke standard filter processing logic
Developers must replicate internal logic manually
The dependency on UpdateBasicRecFilters() makes correct reimplementation difficult
There is a risk of inconsistent behavior compared to the base application
Describe the request
We are requesting the following variables protected so they can be accessed in page extensions:
Why do you need this change?
We are extending Page 7002 "Sales Prices" using a page extension and have a requirement to reuse the existing filtering logic.
The page internally uses the following global variables:
StartingDateFilter
CurrencyCodeFilter
These variables are essential for filtering sales price data and are already used within the standard application logic. However, they are currently not accessible from page extensions, which limits the ability to create consistent and reusable customizations.
When implementing custom actions or logic in a page extension of page 7002, we cannot:
Access the current values of StartingDateFilter and CurrencyCodeFilter
Reuse standard filtering logic already applied by the page
Ensure consistency between standard filtering behavior and custom functionality
As a result, we are forced to:
Duplicate filtering logic manually
Maintain separate custom variables
Risk inconsistencies with future Microsoft updates
This limitation leads to:
Reduced extensibility of standard pages
Additional development and maintenance effort
Increased risk of discrepancies between standard and custom behavior
Less upgrade-safe customizations
On Page 7002 "Sales Prices", the procedure GetRecFilters() is currently defined as local, which prevents it from being accessed or reused in page extensions.
This procedure contains important standard logic responsible for:
Processing record filters
Calling internal filtering logic (UpdateBasicRecFilters)
Assigning StartingDateFilter based on the current page filters
Because GetRecFilters() is local:
Extensions cannot invoke standard filter processing logic
Developers must replicate internal logic manually
The dependency on UpdateBasicRecFilters() makes correct reimplementation difficult
There is a risk of inconsistent behavior compared to the base application
Describe the request