If you follow the recommended practices using the Power Platform CLI for exporting and unpacking solutions in CI/CD pipelines, you can use the `solution add-reference` command to add code-first compon
The first tool I thought of as an example of this type of functionality, was FetchXml Builder, by Jonas Rapp. in FetchXml Builder you can open the results of a query in Excel after getting the results
Two good examples of Power Platform components that aren't easily searched, today, are Canvas Apps and .NET Plugins. Both store some of their information inside of tables in Dataverse that you can sea
That’s why I created Power Platform CLIx (or 'Clix' for short). The tool allows you to explore and run power platform command line functions using a graphical user interface inside of XrmToolBox. With
Currently, Power Automate doesn't support Regular Expression validation and validating emails using the 'contains' condition may not be sufficient. While the specific scenario was for validating email
Until recently, however, you could only create / use Virtual Entity providers that reached out to external APIs via web protocols. The recently enabled ability to reach out directly to Azure SQL from
The error wasn't really specific, but a quick Google search did lead to a solution on [Stack Overflow](https://stackoverflow.com/questions/41618766/powershell-invoke-webrequest-fails-with-ssl-tls-secu
Several months ago after releasing the last feature I'd hoped to include in the tool, the ability to search on related lookups and picklists, I polled the community on what feature I should implement
While I appreciate the recommendation to run my background workflows in Microsoft Flow, and will certainly do it whenever possible. It's unfortunate that only my async processes can live in Flow since
When I first released Universal Search there were a few search scenarios I didn't address. In particular, you couldn't search for records based on the human readable value of picklist and lookup field