[EE 2.1.0] - Edit Product doesn't work after upgrade from 2.0.7 to 2.1.0

[d-gerken]

Steps to reproduce

1. Upgrade Magento EE from 2.0.7 to 2.1.0
2. Log in to backend and browse to products -> catalog
3. Click on any product to edit

Expected result

1. Product can be edited

Actual result

1. HTTP ERROR 500

error log:
PHP message: PHP Fatal error: Uncaught TypeError: Argument 3 passed to Magento\Framework\View\Element\UiComponentFactory::mergeMetadataElement() must be of the type array, null given, called in /var/www/html/vendor/magento/framework/View/Element/UiComponentFactory.php on line 335 and defined in /var/www/html/vendor/magento/framework/View/Element/UiComponentFactory.php:287 Stack trace: #0 /var/www/html/vendor/magento/framework/View/Element/UiComponentFactory.php(335): Magento\Framework\View\Element\UiComponentFactory->mergeMetadataElement(Array, 'schedule-design...', NULL, false) #1 /var/www/html/vendor/magento/framework/View/Element/UiComponentFactory.php(363): Magento\Framework\View\Element\UiComponentFactory->mergeMetadataItem(Array, Array, false) #2 /var/www/html/vendor/magento/framework/View/Element/UiComponentFactory.php(363): Magento\Framework\View\Element\UiComponentFactory->mergeMetadataItem(Array, Array, false)

Workaround:
If you disable following modules it will work properly:
Magento_BundleStaging Magento_ConfigurableProductStaging Magento_CatalogImportExportStaging Magento_CatalogStaging Magento_DownloadableStaging Magento_ProductVideoStaging

[AntonEvers]

Same problem here. Also with Magento 2.1.0 EE upgraded from 2.0.7

[brobie]

Same - Upgraded Magento 2.0 to 2.1.

[satishashilwar]

We are facing the similar issue

[jasonyip2014]

Same problem here

[sanjaycommon]

After disabling this module we have facing another issue
Warning: Illegal string offset 'is_in_stock' in /vagrant/vendor/magento/module-catalog-inventory/Ui/DataProvider/Product/Form/Modifier/AdvancedInventory.php on line 87

[rhoerr]

Same problem here.

[daniel-ifrim]

I've done a hack into that foreach:

if (
    is_string($name) &&
    strcasecmp($name, "schedule-design-update") === 0 &&
    is_null($data)) {
    continue;
} 

The page renders but I can't save the product. I get this error:
Update with id "0" does not exist.
Message is from Magento\Staging\Model\UpdateRepository::get() function.
Also noticed in staging_update table that I had in id column a timestamp value 1467394728 which is actually what is in start_time also. I've created a campaign to test previously. But the start and end time had bugs, had to place only start_time.

On a default Magento EE 2.1 installation I don't get this error but I do get it in a store installation.
Anyway start_time and end_time of schedule update don't seem to work in admin forms (both installs). I don't know now if it's related to current issue.

Anyone has a solution for this ?

Thank you

[jasonyip2014]

Firstly, the issue should happen for the products using custom attribute sets. You just need to go to the database to fix the schedule design update attribute group in the custom attribute sets and then you should be able to access the product edit page. After that, you may be not able to save because of another issue - "Update with id "0" does not exist.". For this following issue, you can solve it by update the value of the column "created_in" in the table "catalog_product_entity" from 0 to 1.

I spent whole day to solve it.

[daniel-ifrim]

@jasonyip2014 This works. I did as you said:
1)
UPDATE eav_attribute_group SET tab_group_code = "advanced", sort_order = 55 WHERE attribute_group_code = "schedule-design-update";
`// This will update default attribute set too but it should have these values already.

2. And moved in admin 3 attributes in each custom attribute set:

• custom_design_from
• custom_design_to
• custom_design
• custom_layout (already there)
  in group Schedule Design Update.
  Now I can see the product page in admin.

UPDATE catalog_product_entity SET created_in = "1";

Just in case, flushed cache storage, cleared var/generation/* and deployed static content in pub/static (not the magento command).
And reindex everything with command magento indexer:reindex

Thank you

[moloughlin]

Updating the value suggested by @jasonyip2014 corrects my product editing issue as well, but I'm still trying to understand why this is necessary. The InstallData.php script for the catalog-staging module explicitly sets the created_in value of all existing products to 0. As we've seen this destroys the ability to update products that existed prior to the 2.1 update, but is there a reason why this value was used? What does the created_in value actually mean in this context?

[wert2all]

Thank you for response, internal ticket MAGETWO-55944 was created.