(Updated) Critical Issue Discovered in 16.0 Release

Note: This is an updated re-post of the previous message. Changes are: the updated release date, and a correction about the actual code change.

Due to rising issues with list pricing in 16.0 Major, the following interfaces have been reverted to the 15.5 version:

• Override  to customListPrice in AbsPart
• basePrice modification in AbsPart
• basePrice modification in DsPart
• Override to upcharge in ProdPart
• upcharge function accounting for option special pricing in SpecOption
• price(SpecOption[]) in DsPData and OfmlData

These changes were originally added to account for the new core PartSpecials system.

Impact of changes:

• The new core QueryDialog will not account for special pricing for now (expected 16.0 Patch 1)
• Any modifications made to account for previous changes may need reversion

The new core QueryDialog does still account for special part numbers and descriptions as well as special option codes and descriptions. The fields for special pricing have been removed for the time being.

Those who may be affected include:

• Anyone who had migrated to the new core PartSpecial and/or OptionSpecial system
• Anyone who had migrated to the new core QueryDialog
• Anyone who made changes to pricing for parts extending AbsPart/ProdPart/DsPart

Anyone who has migrated to 16.0 may need to:

• Test pricing to ensure accuracy
• Implement their own overrides to handle special pricing
• Wait until the core implementation for special pricing is implemented (expected 16.0 Patch 1).

Note that these changes are not an interface change; it is only the behavior that has been updated.

Updated release date

Because this change has the potential to affecting pricing information, and we want to give extension owners the time they need to verify that pricing information is correct, we are pushing back the release of CET 16.0 to MAY 27th. This will shift the normal release window back by a week and a day (also to account for Memorial Day on the 26th).

The Beta distribution (available here) has been updated (for real this time) with the pending fixes to be released on May 27th (the updated first day of release). If you believe that your code is affected by this change, we recommend adding a build of your extension to that box and verify that pricing is correct.

If, after testing, you determine that your pricing is still incorrect in the beta distribution, contact Developer Support immediately. Additionally, you have the option of removing your extension from the 16.0 official distribution to delay updates until the issue is resolved.