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

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

ERROR IMPORT SNL IN ZIP TO DYNAMICS 365

(0) ShareShare
ReportReport
Posted on by

I am trying to import a solution created with Visual Studio 2017 to Dynamics 365. When I save the solution in a .zip file and import from Configuration, this error is thrown:

The solution file is not valid. The compressed file must contain the following files in its root: solution.xml, customizations.xml and [Content_Types] .xml. Customization files exported from previous versions of Microsoft Dynamics 365 are not supported.

Within the solution there are none of the mentioned files. Is it necessary to generate the .zip file in a special way?

Greetings

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Wayne Walton Profile Picture
    13,728 on at
    RE: ERROR IMPORT SNL IN ZIP TO DYNAMICS 365

    Yes, it must be in the exact structure mentioned by the error.  I recommend exporting a solution (even the default solution) from your existing D365 system to see which files do what, because you need an exact mirror of that structure when building a solution from Visual Studio.

  • Community Member Profile Picture
    on at
    RE: ERROR IMPORT SNL IN ZIP TO DYNAMICS 365

    Visual Studio does not generate these files when he creates the solution? Regarding your solution, it is my first solution to import into Dynamics and it does not allow me to export any because they are administrative solutions.

  • Suggested answer
    Wayne Walton Profile Picture
    13,728 on at
    RE: ERROR IMPORT SNL IN ZIP TO DYNAMICS 365

    I don't know what you mean by "administrative solutions".  Solutions are Solutions in Dynamics, and they're not the same as a .sln file in Visual Studio.  

    I also don't know what process you are using to produce a solution file in Visual Studio, because that's not a common process.  The more common process is to compile your plugin, then use the Plugin Registration Tool to install it into a Dynamics dev environment, then make a Solution in Dynamics to export up the chain to test and production.

    So if you're building the solution directly in Visual Studio, you're going to have to explicitly build all the component files yourself.

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…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Community Member Profile Picture

Community Member 2

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#1
UllrSki Profile Picture

UllrSki 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans