Nathaniel Rogers

If you aren't using the temando shipping module at all, you could always stop composer from installing it in the first place ``` "replace": { ... "temando/module-shipping-m2": "*", "temando/module-shipping": "*",...

Getting the same issue as @kanevbg. I was going to make a separate issue for it. Error is when upgrading from M1.9.3.7 to 2.3.5-p2 Can someone point to where the...

A database level check to see the data for easy testing ``` use M1; SELECT COUNT(*) FROM catalog_product_entity_int WHERE attribute_id = (SELECT attribute_id FROM eav_attribute WHERE attribute_code = 'manufacturer'); //...

I've narrowed it down to the PostProcessing step. When a migration is done without that step the manufacturer data is present on the M2 instance. Then running just that step,...

Ok so the manufacturer and color attribute values are lost for some reason. The eav_entity_attribute table (which links attributes with attribute sets) is missing the manufacturer attribute for some reason....

@norgeindian We ended up just commenting out the `\Migration\Step\PostProcessing\Model\AttributeSetLeftoverData` step entirely because we were aware of all the data migrated and nothing was causing issues. It's a shame it didn't...

Thanks for getting back. Yeah, I've recently been trying to do some custom index grid modifications. It isn't easy is it?! Fair enough. Thanks for your time

Is there any further hold ups to this being done?

@fredden that module looks like a good workaround, but this issue was really to have Magento address the issue in the core product. It's been 3 years and no real...

Agree, I have just lost hope that Magento will do anything about it. If anything me closing this just demonstrates that. I no longer make any issues on the magento...