Differences

This shows you the differences between two versions of the page.

--- dynamiczip:install:mods:release:build81:build81 [2019/05/28 13:45] – [Build 81.2] chuck
+++ dynamiczip:install:mods:release:build81:build81 [2019/08/06 16:05] – [Modifications] chuck
@@ Line 39: / Line 39: @@
     * The expiration date has passed.
   * Fixed a bug where the item description lookup in the [[dynamiczip:windows:dz_modify_item_supplement_window|DZ Modify Item Supplement window]] was setting the start or end item description to the item number of the selected item.
+----
+===== Build 81.3 =====
+Compile date: August 5, 2019
+==== Modifications ====
+=== Bogus tax detail supplement records ===
+We discovered that some user installs still had records in the [[dynamiczip:tables:dz_tax_detail_supplement_table|DZ Tax Detail Supplement table]] with exempt tax detail ID's and these unexpected records had their import status set in such a way that was preventing the rate and boundary import from fully and properly updating the related tax schedules. The following query should return zero records:
+<code>
+select * from DZ00400 where TAXDTLID like '%X'
+</code>
+If any records are returned, they can be removed with the following query:
+<code>
+delete from DZ00400 where TAXDTLID like '%X'
+</code>
+We have fixed this problem by including a step in the import that automatically removes these bogus records. The above workaround is only required if you encounter this problem but are unable to upgrade to the latest build.
+=== Geocode not found ===
+When an address has a zip code but no city and/or state, the DynamicZip tax schedule selection process's selection message was "Geocode not found". While it is true that no geocode was found, the schedule selection process could have continued and returned the default tax schedule for that zip. This update fixes this problem.
+=== Tax Schedule not found ===
+The [[dynamiczip:glossary:thomson_reuters_onesource_compete_plus|Thomson Reuters ONESOURCE Complete+ Database]] contains lines that have a city tax but that tax is for a city not found in the line's zip and therefore that tax schedule doesn't get selected. Please see [[dynamiczip:troubleshooting:issues:usps_city_name_not_the_incorporated_city_name|USPS city name not the incorporated city name]] for more information. These relatively rare situations are now handled by importing the foreign city tax rate as a district tax rate which prevents the resulting schedule from being rejected due to the city name conflict.
+== Result ==
+This fix creates a county local district tax for the foreign city tax rate. The resulting tax schedule includes this county local instead of the foreign city tax detail. This results in the correct tax being charged. It also results in the correct USPS preferred city name being used for the zip. The downside is that more than one tax detail now exists for the same city tax. However, if DynamicZip reports include the location code in their sort options, the reports can combine them back into a single total.