While trying to import the solution (patch), we were getting the below error. “Expected non-empty Guid” There was hardly any detail in the log file also We tried removing the solution component one by one in our source environment and trying the import again in the target environment. Eventually removing the Pages (custom page) allowed … Continue reading “Fixed – Expect non-empty Guid while…
Continue Reading Nishant Rana’s Article on their blog
Fixed – Expect non-empty Guid while importing solution in Dynamics 365/ Dataverse
While trying to import the solution (patch), we were getting the below error. “Expected non-empty Guid” There was hardly any detail in the log file also We tried removing the solution component one by one in our source environment and trying the import again in the target environment.
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)
- Dyn365CE23 April 2024Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)
- Dyn365CE22 April 2024Versioning and Drafts for Solution-based Cloud Flows – Power Automate