web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

CRM Online SP1, - Solution Import fails with error Invalid XSD validation - solutionaction attribute not declared

(0) ShareShare
ReportReport
Posted on by

I face an issue while importing a solution to CRM online Org from our master (on-premise) ORG which is also installed with SP1 and solution is exported with target environment as 6.1.  We are getting below error,

Error: "The import file is invalid. XSD validation failed with the following error: 'The 'solutionaction' attribute is not declared.'."

I  can notice that in my customization XML  I could see solutionaction attribute in the anscestor node of an entity form.  "<ancestor id="{1fed44d1-ae68-4a41-bd2b-f13acac4acfa}"  <<<<<ERROR LOCATION>>>>> solutionaction="Removed" />" 

Any idea why I have this attribute if not supported by CRM XSD ? And how I can proceed ?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    NicksTuk Profile Picture
    1,833 on at

    Most likely you have a solution exported from a different version, or started in a version prior to SP1. The attribute is probably located at the wrong level in the XML. Try exporting a simple solution from an SP1 organization, and see what the location of the attribute is in there, so you can move it accordingly in your solution.

  • Community Member Profile Picture
    on at

    yes, we had CRM 2013 6.0 on both master (onpremise) and online . We recently installed SP1 on both master and online orgs and updating the solns form master to online. I can't see this attribute solutionaction in any ancessator node however I can see this attribute in many other nodes of the customization xml.  I could remove this attribute and try, but trying to understand how it came here and why it not comply with XSD schema .

  • Suggested answer
    Bruno Lucas Profile Picture
    5,421 on at

    have you used a tool that installs internally for development? like the ribbon workbench tool? I had a similar problem. I installed the tool on a dev instance, edited the ribbon. when I tried to import the solution to the QA environment, it presented a similar error. the tool added a dependency to the Silverlight webresource that has the interface. since the destination did not have the ribbon workbench tool installed, the solution from dev could no be imported.

    you may have something similar. some other dependency you have on your master CRM. something that is installed there or modified there on another solution and is not present on your online crm.

  • Johao Larios Profile Picture
    1,795 on at

    Hi, Bruno,  did you fix this ? I'm having exactly the same problem.

    Regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans