I have also tried to double the model and id-colums, to change place of these columns and many other variables, but for some reason the manager doesn't see these two columns..
I have also tried to double the model and id-colums, to change place of these columns and many other variables, but for some reason the manager doesn't see these two columns..
Could it maybe has something to do with this? (when I try to make a new template, the two missing columns are already there and cannot being moved). I have the impression that the manager sees only the manually attached template fiels, not the two that are already there, because these two columns are missing.....
![]()
Last edited by LadyoftheCave; 24 Sep 2017 at 12:00 PM.
Nope, when you create a DbIo template, there are sometimes (like for the Products handler) database fields that are required. The Products handler requires that the v_products_id and v_products_model fields both be present in the import ... even though (as you found) the v_products_id value has no bearing when the product is being created.
You'll need to keep the v_products_id column (set that value for new products to 0) and supply a unique v_products_model value for a new product to be created.
When creating a new product, you'll also want to make sure that you have the v_categories_name column set to identify the category "tree" associated with the to-be-added product's master-category.
When you're performing any kind of import, I suggest that you first perform an Import (Check-only) first. That processing will do every step of the import ... except that the database is not updated. You can then see what will happen before actually committing the information to your database.
Once the import is finished, a link shows next to the action-selection dropdown that reads View import details; click that link and a popup will display showing you the status of that import.
After you've verified your import-csv using Import (Check-only), that's the time to use Import (Full) which will actually write the requested information to your database.
thank you very much,
I will try that out now :)
It turns out that the message that @LadyoftheCave was receiving was because the import CSV file was using a semi-colon (;) instead of the more traditional comma (,) as the field delimiter.
Updating the DbIo's Configuration->DbIo Manager Settings->CSV Delimiter to ; allows the import to proceed without error.
Bookmarks