Metadata API Deployment fails from Spring '17 to Summer '17 if an Assets Page Layout has one of the following fields set to Read-Only: Account, Produc
Last updated 2017-10-14 ·Reference W-3979294 ·Reported By 12 users
If you have retrieved metadata from a Spring '17 (or prior) org, with an Asset Page Layout that had the Account, Product2 or Contact fields set to Read-Only, then deploy that package to a Summer '17 org, it fails with the following:
Field:AccountId must not be Readonly
Field:Product2Id must not be Readonly
Field:ContactId must not be Readonly
Deploy a Metadata API package, containing an Asset Page Layout that had the Account, Product2 or Contact fields set to Read-Only, which was retrieved from a Spring '17 (or prior) org to a Summer '17 org.
Update the Assets Page Layout in the Spring '17 org to make the fields not Read-Only, then retrieve the metadata again
Edit the Assets *.layout definition file(s) in the package and change the "behavior" tag for the field(s) to "Edit"
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.