While importing a solution we received \u201cSchema Validation Failed\u201d and it said \u201cThe ‘label’ attribute is not declared\u201d.<\/p>\n According to the error the \u201clabel\u201d attribute which is been found in the solution i.e. in the customization.xml file is not valid.<\/span><\/p>\n Cause of the issue<\/strong><\/span>:<\/p>\n This issue occurs when you save a copy of system view of an entity which you cannot edit.<\/p>\n For example: Quote Product Inline Edit View from quote product entity, Order Product Inline Edit View from order entity or All Sales Team Members view from connection entity etc.<\/p>\n When you select option \u201cSave As\u201d view CRM will create copy of this view but the schema format of this view is not in a required format. When you will open this view in solution xml you will notice that columns which has been copied from the existing view has invalid format as show below i.e. label = \u201cRole\u201d is not supported.<\/p>\n <cell name=”record2roleid” width=”136″ LabelId=”query.4E3600FA-B9C8-49F4-B69A-51EBA06D9BDF.cell.role.label” label=”Role” \/><\/p>\n Resolution<\/strong><\/span>:<\/p>\n There are two solutions to resolve this issue:<\/p>\n In our case we have copied a connection view \u201cAll Stakeholders\u201d so we are providing steps considering connection entity.<\/p>\n 1. Modify the view from entity customizations<\/p>\n a) Go to Settings –> Customizations –> Customize the System –> Expand the entities tab and open a connection entity views<\/p>\n b) Open the view and remove the existing columns which have been copied from previous view and add them back in a view<\/p>\n c) Save the view and publish the customization. 2. Modify the customization.xml file manually<\/p>\n a) Extract your solution (.zip) file that you are importing f) Remove the label=\u201dColumnName\u201d from the entire xml. If you know which view you have saved from existing managed view then the first option will be the easiest way to resolve the issue. If you do not have idea from which view this would be causing, then you can go with the second solution.<\/p>\n","protected":false},"excerpt":{"rendered":" Recently we came across with the issue while importing a solution from our dev environment to another test environment. So we thought of sharing this with everyone so that others do not face the same problem. Issue: While importing a solution we received \u201cSchema Validation Failed\u201d and it said \u201cThe ‘label’ attribute is\u2026 Read More: Schema Validation error while importing Solution »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,21,22,24],"tags":[392,919,1550,1643],"class_list":["post-477","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-crm-2013","tag-import","tag-schema-error","tag-solutions"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t![\"img1\"](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/05\/img15.jpg\")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
\nd) After that re-export the solution and import in your target environment.
\ne) The solution will import successfully.<\/p>\n
\nb) You will find the customizations.xml file in the extracted folder
\nc) Open this customizations.xml file
\nd) Find for a keyword \u2018 label=\u201d\u2019 find the keyword label followed by space so you can easily find the exact location.
\ne) You will find the error\u00a0location as highlighted in the below screenshot:<\/p>\n<\/a><\/p>\n
\ng) Then save the xml file and zip all the components from the extracted solution and import it.
\nh) This will import your solution successfully.<\/p>\n