Are you creating Dataverse tables in the Maker portal using the "Create a new table" option with the "Start from blank?" Then you need to know about this known issue.
I recently encountered a problem after adding a new table to my solution. I created it in the Maker portal using the "Create a new table" option with the "Start from blank" experience. After configuring everything and exporting it for deployment, during the import process my client got a long list of missing dependencies, all related to the new table and its attributes—even though everything was included in the solution (I triple checked). It was strange…
After talking to other experts and trying many fixes when I was about to give up, I found out it is a known issue. When exporting a solution that includes a newly created table from the Maker portal, the import into a destination environment can fail due to missing dependencies related to the table's attributes.
The workaround?
Export the solution as unmanaged from the environment.
Import it back into the source environment.
Export the solution as a managed solution from the source environment.
This approach resolved the missing dependencies, and my client could successfully import the solution into their environment.
Hope this helps anyone facing similar challenges!
About Me
I'm Leoza Kabir Barker, a Functional Consultant at XRM Vision with a focus on the Power Platform. Through my expertise, I aim to streamline processes, optimize operations, and maximize productivity.
Connect with Me
Blog: www.leozakabirbarker.com
Commentaires