Yes and no. Can't recall someone indicating that just because they "updated" the record(s) (submitted the same file exported as an import where each record has a unique primary key) that the product became linked.
So, here's how a linked product can be generated when using just EP4 (I can't at the moment speak for the bookx addition you've made) when reviewing the import file:
If a record has a primary key that matches an existing primary key in the database but the category is different, a linked product will be created/updated.
Note, if at import the database doesn't contain the associated primary key, but the file has two entries in it where each has a different category, then when the second record is encountered, that second record will cause the product to be linked to the new category and all associated data will be updated to match the most recent occurrence.
That's really all that will create a linked product.
So to avoid generating linked product, always use a unique primary key for each individual product. EP4 has two types of primary key available with the possibility to code additional: products_model and products_id.
To remove linked product, I suggest rereading the instructions, but by setting a row's status to 7, then the category identified on that row will become the master_categories_id. The current master_categories_id will be unlinked from the product. If there are multiple linked categories for a single product then it may be advisable to use this process for all records and then to "add" those desired to be linked after the linkages have been reduced down to a single master_categories_id. There are a number of ways to work through this situation, but that particular method would resolve the situation for all cases.
If you are getting linked product on import, either the primary_key data already exists or is duplicated in the import or there is something wrong with the bookx addition.
Bookmarks