jowells1 / automatepowerappschecker Goto Github PK

Need to update the Export-CrmSolution command to use $solution.uniquename:

From:
$s = Export-CrmSolution -conn $crmSvc -SolutionName $solution.friendlyname -SolutionFilePath $solutionsDirectory -SolutionZipFileName $sName"_"$sVersion".zip"

To:
$s = Export-CrmSolution -conn $crmSvc -SolutionName $solution.uniquename -SolutionFilePath $solutionsDirectory -SolutionZipFileName $sName"_"$sVersion".zip"

Need to be able to use different accounts if we need to upload files to Azure blob storage.

For solutions that are over 30 MB in size, the solution needs to have an option to upload to Azure blob storage and a SAS URI must be provided. Documentation for this is found under the FileUnderAnalysis parameter here:
https://docs.microsoft.com/en-us/powershell/module/microsoft.powerapps.checker.powershell/invoke-powerappschecker?view=pa-ps-latest#parameters

Need to document that NuGet provider version 2.8.5.201, or greater, is required.

If a customer already has a solution file, they should be able to submit that solution file rather than having to connect to CDS to export a solution.

Feedback provided:
Fix 1: prevents default solution not to be excluded when Base Language is different than English
Replace:

With:

Fix 2: prevents failure of Export-CrmSolution when Friendly Name is different than Unique Name (this usually happens when Friendly Name has spaces or characters with accents.
Replace:
$s = Export-CrmSolution -conn $crmSvc -SolutionName $solution.friendlyname -SolutionFilePath $solutionsDirectory -SolutionZipFileName $sName""$sVersion".zip"
With:
$s = Export-CrmSolution -conn $crmSvc -SolutionName $solution.uniquename -SolutionFilePath $solutionsDirectory -SolutionZipFileName $sName""$sVersion".zip"

Need to document that when having to add the AzureAD and PowerApps Checker PowerShell modules, will get prompted to trust the repository. Need to clearly document this.

A suggestion was provided to export and analyze managed solutions.

Clearly document that PowerShell x64 is required to use the correct AzureAD modules.

Currently, the script prompts for credentials but does not define what the credentials are for. Need to be more descriptive with this process to note that the initial credentials are used for D365. There is a check to see if you want to use different credentials for the Azure Authentication. Need to also document it needs to have System Admin or System Customizer role.

Based on customer testing and the following Issue for Microsoft.Xrm.Data.PowerShell, going to update the command to use oAuth:
seanmcne/Microsoft.Xrm.Data.PowerShell#387

When trying to process a large solution file into the Azure blob storage, using the container fails when there are no storage accounts..

SolutionType attribute was being used to prevent retrieving the Default Solution. Since the Default Solution in CDS is uniquely named, needed to find a way to filter that out. Will need to look at conditional logic for online and on-prem to use different filtering criteria to prevent the default solution from being exported.