User Tools

Site Tools


dynamiczip:install:mods:release:build77:kampdatabase_import_aborting_if_a_state_in_the_group_is_not_in_the_statesincluded.txt_file

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
dynamiczip:install:mods:release:build77:kampdatabase_import_aborting_if_a_state_in_the_group_is_not_in_the_statesincluded.txt_file [2016/04/13 21:35] chuckdynamiczip:install:mods:release:build77:kampdatabase_import_aborting_if_a_state_in_the_group_is_not_in_the_statesincluded.txt_file [2016/04/13 21:40] (current) chuck
Line 2: Line 2:
  
 Prior to [[dynamiczip:install:mods:release:build77:build77|Build 77]] a [[dynamiczip:windows:dz_rate_and_boundary_import_window|rate and boundary import]] with the Import Source set to KampDatabase would abort if any state included in the Group ID did not exist in the [[dynamiczip:glossary:states_included_file|StatesIncluded.txt file]]. Prior to [[dynamiczip:install:mods:release:build77:build77|Build 77]] a [[dynamiczip:windows:dz_rate_and_boundary_import_window|rate and boundary import]] with the Import Source set to KampDatabase would abort if any state included in the Group ID did not exist in the [[dynamiczip:glossary:states_included_file|StatesIncluded.txt file]].
 +
 +Prior to Build 77, the import report included an error line for each such state and the import would abort at that point.
 +
 +For Build 77 and later, the import report includes a warning line for each such state and the import continues without aborting.
 +
 +The workaround for builds prior to Build 77 is to simply remove these problem states from the Group.
  
dynamiczip/install/mods/release/build77/kampdatabase_import_aborting_if_a_state_in_the_group_is_not_in_the_statesincluded.txt_file.1460583342.txt.gz · Last modified: 2016/04/13 21:35 by chuck

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki