Shipping Method Change not Triggering Tax Schedule Update

When you select or edit a shipping method, Microsoft Dynamics GP may update the Tax Schedule ID field based on the Shipping Type However, Microsoft Dynamics GP fails to force the document tax schedule ID field's change script to run. As a result, the DynamicZip Base On Customer object trigger will fail to fire and the tax schedule ID will not get copied back to the sales, freight and/or miscellaneous tax schedule id fields as expected.

• This problem applies to transactions entered in the Receivables Transaction Entry window and the Payables Transaction Entry window.

• As of Build 72 this issue has been corrected. We added an Object Trigger to DynamicZip that uses the Force Change command to fix this problem. The DynamicZip object trigger will fire whenever the Shipping Method field is modified by the user. This trigger will cause the Tax Schedule ID change script to run the next time focus moves off the Tax Schedule ID field.

We have three suggested workarounds that you can choose from:

1. The easiest workaround is when you can manually select the Tax Schedule ID by first clicking the Tax Schedule ID lookup button, and then pressing the Select button on the Tax Schedules window. This should trigger GP to correctly bring the Tax Schedule into the document and calculate the tax accordingly. NOTE: The Tax Schedules window should automatically be focused on the correct Tax Schedule ID. If it is not, you must manually select which Tax Schedule ID to use prior to pressing the Select button.
2. You could do an edit-cut of the documents tax schedule, move the focus off the tax schedule field, move back onto the field and then edit-paste the value back in.
3. Manually editing the Purchase, Freight, and/or Miscellaneous Tax Schedule ID(s) by opening the Tax Schedule ID expansion window from within the Payables Transaction Entry window or the Sales, Freight, and/or Miscellaneous Tax Schedule ID(s) by opening the Tax Schedule ID expansion window from within the Receivables Transaction Entry window should work as well.

This irregularity was initially discovered in Dynamics R4.

Microsoft Dynamics GP Known Issues