Metadata API Deployment fails from Spring '17 to Summer '17 with "Field:TagCsv must be Readonly"
Last updated 2022-02-10 ·Reference W-3957216 ·Reported By 21 users
If you have retrieved metadata from a Spring '17 (or prior) org, with ContentVersion Layout included, then deploy that package to a Summer '17 org, it fails with the following:
Field:TagCsv must be Readonly
Deploy a Metadata API package containing ContentVersion Layouts, retrieved from a Spring '17 (or prior) org, to a Summer '17 org.
Remove the ContentVersion Layout references from your package.
Edit the ContentVersion Layout definition file and change the TagCsv section to:
Reported By (21)
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.