rappen / powerappschecker

PowerApps Checker tool for XrmToolBox

Welcome to @rappen!

🔢 The Numbers

---

💬 The Social

---

🛠 The Stuff

• A bunch of tools for the XrmToolBox
• Some repos with helpers and tools for Microsoft Dataverse development
• Example and demo repos from sessions I've done - see jonasr.app/speaking
• Some shared stuff from my blog at jonasr.app
• Most popular tool is used close to a million times yearly (2020) - see fetchxmlbuilder.com

---

🚀 The Releases

	Repo	NuGet	AzDO	GitHub
🐤
💻

powerappschecker's Issues

Analyze multiple solutions

Add the possibility to select multiple solutions (or local solution files) for analysis.

Allow for SAS Uri to be passed in addition to the existing CDS and local file options

There is a 30 MB limit for the upload API. This also allows the flexibility for a partner to provide a SAS URI to a customer instead of having to exchange the entire package/solution.

Add France to the geographies list

https://france.api.advisor.powerapps.com is now available

For auth allow the user to select their account

There will be cases where a user needs to login as a different user in a different tenant. It appears that the current configuration that you are using is setup with a PromptBehavior of something such as Auto where is leverages any cached tokens and can end up with an error, such as below. In my case I have an application ID that I want to use in a different tenant. I am logged in already using my primary tenant and cannot switch the user within the confines of the XrmToolBox app. Consider having it as SelectAccount on the first login and afterwards using Auto. Here is a small snippet of what is done in our PowerShell module:

promptBehavior = alreadyAuthenticatedUser ? PromptBehavior.Auto : PromptBehavior.SelectAccount;

Then pass this prompt behavior to AcquireTokenAsync().

AADSTS700016: Application with identifier 'xxxxxxxxxxx' was not found in the directory 'xxxxxxxxxxxxxxx'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

Include an other option for the Geography dropdown and allow for a custom URL to be entered

I would suggest an approach similar to the connection on the devops task where the user can specify the URL themselves. This will be valuable when we add new geographies or needing to use a test URL.

Error when connecting PAC

I kept getting the error "Cannot convert object of type 'System.String' to type 'Rappen.XTB.PAC.Helpers.Fix'" when I open this plugin in XrmToolBox.

I also got it after a successful sign in from the Connect PAC screen too. Event I tried to ignore it by clicking the OK button, I can get to a point to analyze the solution file, although I can't select the rulesets etc., then a lot of errors started to popup when it rendered the grid view to display the results.

I have tried deleting the XrmToolBox storage folder in AppData and deleting the entire XrmToolBox app and downloading the latest again, same error. The plugin is also the latest version.

Tried open XrmToolBox in admin model, same error ... I can't figure out what caused this error.

Save PAC service info

Many times the same PAC service is used for several CDS environments, so it would help to be able to save/open PAC service settings.

---

• Deployment: Online
• DB Version: 9.1.0.15051
• XTB Version: 1.2020.2.37
• Tool Version: 1.2019.12.2

Custom Rulesets

Add the possibility to save currently selected rules as a custom ruleset.
Could be presented in the same dropdown as the official rulesets, but will invoke analysis using all checked rules instead of selected ruleset.

Include an option for selecting other languages as provided by the Power Apps checker web API

The service support all the languages that Power Apps does. The list of codes are below. You can also find them as part of the ValidationSet for the LocaleName parameter in the PowerShell cmdlets. You can put the language code in the Accept-Language header of the rule and analyze API and it will do the translations for you including the results in the SARIF. You may need to tweak your parsing of the SARIF a bit to support it. We do support multiple languages as well passed in the header. We don’t currently have ruleset names being translated.

"bg", "ca", "cs", "da", "de", "el", "en", "es", "et", "eu", "fi", "fr", "gl", "hi", "hr", "hu", "id", "it", "ja", "kk", "ko", "lt", "lv", "ms", "nb", "nl", "pl", "pt-BR", "pt-pt", "ro", "ru", "sk", "sl", "sr-Cyrl-RS", "sr-Latn-RS", "sv", "th", "tr", "uk", "vi", "zh-HANS", "zh-HANT"

Handle solution export >2 minutes

The solution export times out after 2 minutes.
Fix it.

Buttons Analyze and Authenticate inactive despite proper setup

Hi,

I set the tool up last week as suggested and everything worked as expected. Unfortunately I am now neither able to Authenticate via Connect PAC, nor to Analyze, since both buttons are inactive.

The Azure App Registration is setup as suggested.
Any idea how to solve this? For us, it seems to be the only solution to validate our code against the App Source guidelines, since the ODCA tool is inaccessible. Thank you!

Best

Mathias

[Minor] Clicking on empty severity "-" causes an unhandled exception

Without running the analysis, if you happen to click on one of the severity count text boxes that contain "-" it causes an exception. It appears to be a binding issue.

System.ArgumentNullException: Value cannot be null.
Parameter name: dataSource
at System.Windows.Forms.BindingContext.HashKey..ctor(Object dataSource, String dataMember)
at System.Windows.Forms.BindingContext.GetKey(Object dataSource, String dataMember)
at System.Windows.Forms.BindingContext.EnsureListManager(Object dataSource, String dataMember)
at System.Windows.Forms.BindingContext.get_Item(Object dataSource)
at Rappen.XTB.PAC.DockControls.SarifControl.txtResultCountInfo_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.TextBoxBase.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)