1b.app
Link copied -

Vipadkovo united up to 40 commodity positions into one. How to correct?

Good afternoon. Vipadkovo chi nі, but it so happened that they united in one sack of dozens of commodity positions. The whole story is in turmoil: come, sell and show up - everything was taken in one commodity position under the number 3578. What is the ability to turn everything around like a boulo (resurrection from backup and fall, so since the moment of the manifestation of this problem has already fallen for a hundred years)? Could you please please, let's clear up the leftovers and enter the data in a new way?
Original question is available on version: ru

Answers:

Hello.
Unfortunately, I don't really understand the problem.
You can use examples (links) to describe what happened, what actions you performed and what happened as a result. Perhaps this will clarify the overall picture and I can offer you a solution.
02.06.2021, 14:28
Original comment available on version: ru

I have a suspicion that everything happened through the double click of the "Combine products with the first selected" button (already removed from the panel) in the panel of mass operations from the products. Tobto mentally:
* - maybe 40 goods, which were seen at the same time for some operation (for example, adding the date of completion of the reduction)
* - then press the "Combine products" button
* - 39 products known to be removed
* - the result - all the information that was found on the product cards (photo, characteristics, availability in warehouses, sales history and ruhіv for 40 products) - is collected from one card for the request: https://bigcatch.crm-onebox.com/admin /shop/products/3578/edit/
03.06.2021, 06:48
Original comment available on version: ru

If there were no changes (any warehouse operations) for this product (remains, etc.), then in theory you can:
1. you need to deploy a copy of the database from the dump for the required number (before the incident)
2. write scripts that, for the specified products that have been merged (they still need to be found), will check all the data that has been merged from a copy of the database and change similar records in the current database.
some data will need to be restored to the dump (the same additional fields, etc.), which could already change in the same way in the combined product
Such manipulations will take about 10 hours.
But I cannot give any guarantees that everything will be perfect, because some of the data could have already been changed - after all, a lot of them are involved in the merging (additional fields, filters, price levels, etc. - all this will be restored to moment of the dump, unless we can leave it as it is only in the current merged product).
03.06.2021, 16:24
Original comment available on version: ru

Thank you for your advice. I pressed the update from the backup, so it was a lot of changes according to the data. They made a decision to take a path to pererakhunka.
07.06.2021, 13:58
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment