search

yashag2255 / PrintIt-Component

PowerApps Component Framework for Canvas App
GNU General Public License v3.0
12 stars 4 forks source link

Import Solution #4

Open onelove2283 opened 4 years ago

onelove2283 commented 4 years ago

I cannot import the solution.

fkomizi commented 4 years ago

I cannot import the solution either. Here is the error I receive

An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support. : Microsoft.Crm.CrmException: CustomControls with Name test01.test01 Import Solution Failed with following error: Publisher prefix contoso for this control test01.test01 does not match the prefix ya for the solution with Id 81782519-f283-4e9d-9f90-f44eb5b2f9e4. at Microsoft.Crm.Tools.ImportExportPublish.ImportCustomControlsHandler.ImportItem()

yashag2255 commented 4 years ago

Updated the Managed and unmanaged solutions so that can be directly imported.

suresh-git2020 commented 4 years ago

@yashag2255 - I have tried importing the managed and unmanaged set of codes and it still doesn't work. It is trying to create the schema that you have defined as btd_test01.test01 under the principal user name... etc., and then fails. Below is the error

Import Solution Failed: CustomControl with name test01.test01 failed to import with error: Principal user (Id=**** type=8, roleCount=4, privilegeCount=808, accessMode=0), is missing prvCreateCustomControl privilege (Id=**on OTC=9753 for entity 'customcontrol'. context.Caller=****. Or identityUser.SystemUserId=**, identityUser.Privileges.Count=1884, identityUser.Roles.Count=0 is missing prvCreateCustomControl privilege (Id=) on OTC=9753 for entity 'customcontrol'.

BMassmann commented 3 years ago

@yashag2255 Good morning, I was curious if there was a solution for this, I am experiencing the same problem.

suresh-git2020 commented 3 years ago

@yashag2255 Good morning, I was curious if there was a solution for this, I am experiencing the same problem.

It was purely an access issue for myself. If you are using an official O365 account, you might have to check with your Power Platform admin to get full access for importing/creating a solution. @BMassmann