Dynamics Ax 4.0
Currently our PriceDiscTable contains a variety of records that are at Table, Group, All levels. Each of these records are further grouped by a new field we introduced that groups them into contracts, promotions and lastly list price (price lists).
The contracts coincide with the Table grouping of customers and the promotions are offered for customers grouped at Group level (and sometimes Table). The list prices are only for Group or All level.
Although there exists a conflict between the promotion type records at Group Level and list price type records at Group level - 90% of the time these work fine as the list price records are 'older' and therefore fetched only if the promotion record doesn't exist.
The problem only occurs when the list price is updated when a promotion price already exists. We want the promotion price to be fetched, but as he list price is newer - the list price is fetched instead.
If that makes sense, please can someone tell me how;
a. Ax handles such a situation and how it determines which is the newer record in the PriceDiscTable? (the created/modified date time fields are not populated in this table)
b. find a way to refresh the promotion prices directly within PriceDiscTable to make Ax think they are newer (without having to reimport and post a new journal)?
c. if, there is another solution? (Other than prioritizing by our grouping as well)