Answered

Microsoft Dataverse for Teams - Import Solution Error - imported solutio contains events/form libraries which is not supported for CDS lite

(0) Share

Report

Posted on by kubalaml

I'm working on a solution using Microsoft Dataverse for Teams. I have been exporting this solution from one team to another and it works about every other time. When it fails, I just delete the existing solution and import the solution as a brand new solution instead of an upgrade. This time though it is failing and even deleting the original solution does not work. Here is the error I am getting when importing.

Formid 'de94e97d-9f01-4e51-aa75-ef8d62ef2ff9' being imported contains events/form libraries which is not supported for CDS lite. Removing the events/form libraries from the formxml will resolve the issue

I don't know what 'events/forms libraries' is referring to. Here is what the log says.

But 'crdcb_micachievement' is just a table and I created it the same as the other tables.

Is there some form attached to this table that I need to get rid of? Can I edit the solution zip file somehow to remove this refence?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @kubalaml,

When you create the solution and its tables and components in the standard Dataverse environment, you have to make sure you don't include or activate any features that are not supported in Teams. There seems to be some related to that form. Check if the form contains any special controls, script libraries, etc. Also you can try to create a new simple form with minimal fields, no controls and form libraries, and delete that old form.

Let me know how that goes...

Was this reply helpful? Yes No
Verified answer

kubalaml 88 on at

Like (0)

Report
Copy link

Link copied!

I didn't add anything special. At least I don't think I did. I think the most I did was modify the views by adding some columns, sorting, and filtering. I was able to get the import to work eventually though by removing all <FormXML> references from customizations.xml file in the solution.

Was this reply helpful? Yes No