User Tools

Site Tools


dynamiczip:glossary:zipsales_database_detailg_file

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
dynamiczip:glossary:zipsales_database_detailg_file [2015/05/18 22:12]
conni
dynamiczip:glossary:zipsales_database_detailg_file [2017/09/12 22:25] (current)
conni
Line 3: Line 3:
 The DynamicZip [[dynamiczip:​features:​import:​rate_and_boundary_import|Rate & Boundary Import]] process utilizes the information contained in this [[dynamiczip:​features:​import:​CCH]] [[dynamiczip:​glossary:​zipsales_database|ZIPsales Database]] file only when the breakdown details total the same tax rate as the source file detail being overridden. The DynamicZip [[dynamiczip:​features:​import:​rate_and_boundary_import|Rate & Boundary Import]] process utilizes the information contained in this [[dynamiczip:​features:​import:​CCH]] [[dynamiczip:​glossary:​zipsales_database|ZIPsales Database]] file only when the breakdown details total the same tax rate as the source file detail being overridden.
  
-As of [[dynamiczip:​install:​mods:​release:​build73:​build73|Build 73]] all of the records in the ZIPsales Database Detailg File are assumed to represent a break down of taxes contained in the Local.txt file. This is in response to instructions (from [[dynamiczip:​features:​import:​CCH]] technical support incident) that appear to contradict the [[dynamiczip:​glossary:​zipsales_database|ZIPsales Database]] documentation (DATABAS2.DOC). As the current situation seems to be a data issue rather than a documentation issue, this assumption can be turned off by modifying your [[dynamiczip:​glossary:​dex_ini_file|Dex.ini]].+As of [[dynamiczip:​install:​mods:​release:​build73:​build73|Build 73]] all of the records in the ZIPsales Database Detailg File are assumed to represent a break down of taxes contained in the Local.txt file. This is in response to instructions (from [[dynamiczip:​features:​import:​CCH]] technical support incident) that appear to contradict the ZIPsales Database documentation (DATABAS2.DOC). As the current situation seems to be a data issue rather than a documentation issue, this assumption can be turned off by modifying your [[dynamiczip:​glossary:​dex_ini_file|Dex.ini]].
  
 ---- ----
 [[dynamiczip:​glossary:​Glossary]] [[dynamiczip:​glossary:​Glossary]]
  
dynamiczip/glossary/zipsales_database_detailg_file.txt ยท Last modified: 2017/09/12 22:25 by conni