I was doing some import diagnostics tonight, and noticed that some relatively new categories that should have been already existing, but not marked active, were not imported in tonight's import.
Here is a snippet of the import CSV (with header):
CATEGORY_CODE,CATEGORY_NAME,CATEGORY_ACTIVE,CATEGO RY_PARENT_CODE
cat_flanges_SplinedBore_28Spline_1-493-28invol,Ø1.493 - 28 Involute Spline,0,cat_flanges_SplinedBore_28Spline
I would have expected this category to be created, but set inactive. Instead, it simply didn't exist.
I found a part that should belong to this category, but in our master database the category code was misspelled. Therefore, the routine we use to set active categories didn't flag it as active. I presumed I could simply assign it in the Miva admin, but it didn't exist after our import tonight.
Could this be a bug? It seems if we have our category import set to "add new/update existing" categories, that it should add even the inactive categories. I swear it used to, but I suppose that may have been when we were using a flat file import and not the .csv.
Here is a snippet of the import CSV (with header):
CATEGORY_CODE,CATEGORY_NAME,CATEGORY_ACTIVE,CATEGO RY_PARENT_CODE
cat_flanges_SplinedBore_28Spline_1-493-28invol,Ø1.493 - 28 Involute Spline,0,cat_flanges_SplinedBore_28Spline
I would have expected this category to be created, but set inactive. Instead, it simply didn't exist.
I found a part that should belong to this category, but in our master database the category code was misspelled. Therefore, the routine we use to set active categories didn't flag it as active. I presumed I could simply assign it in the Miva admin, but it didn't exist after our import tonight.
Could this be a bug? It seems if we have our category import set to "add new/update existing" categories, that it should add even the inactive categories. I swear it used to, but I suppose that may have been when we were using a flat file import and not the .csv.
Comment