Disclaimer

The information published on Mahsud's Dynamics CRM Blog is provided for general informational and educational purposes only. It reflects the author's personal experience working with Microsoft Dynamics 365 and the Power Platform and is not official documentation or guidance from Microsoft.

No Professional Advice

Nothing on this blog should be treated as formal technical, legal, or professional advice. Configuration steps, code samples, and recommendations are shared as-is, and you should always test changes in a non-production or sandbox environment before applying them to a live system.

Accuracy and Currency of Content

Microsoft Dynamics 365 and the Power Platform are updated frequently, and features described in older posts may change, move, or be retired over time. While reasonable effort is made to keep content accurate at the time of publishing, no guarantee is made that every post reflects the current state of the platform.

External Links

This blog may link to third-party websites, including official Microsoft documentation, community blogs, and tools. These links are provided for convenience, and their inclusion does not imply endorsement. We are not responsible for the content, accuracy, or practices of any linked external site.

No Liability

Use of any information, code snippets, or instructions found on this blog is entirely at your own risk. The author is not liable for any loss, damage, or issue arising from actions taken based on content published here, including but not limited to data loss, downtime, or configuration errors in a production environment.

Trademarks

Microsoft, Dynamics 365, Power Platform, Power Automate, and related marks are trademarks of Microsoft Corporation. This blog is an independent publication and is not affiliated with, endorsed by, or sponsored by Microsoft.

Questions

If you have questions about this disclaimer, please reach out through the contact form on this blog.

Comments

Post a Comment

Popular posts from this blog

Dynamically Populating Ribbon Flyout Menu in Unified Interface

Image
My previous post  Dynamically Populating Ribbon Flyout Menu   describes the way to add flyout menu buttons dynamically, but that was limited to web client and was not working in unified Interface. As per my R&D and support ticket with Microsoft, we are still not able to add dynamic Flyout menu buttons directly in Unified Interface (UCI). The issue is due to the dynamic buttons don't detect the command that we were adding through our JS code, so we need to attach that command to a hidden button so that internally the command is visible. Following are the two steps we need to achieve the dynamic flyout in both Web client and unified interface. These steps are actually a continuation of my previous post . Step#1 : Adding a button, where you need to call the command that we have used for dynamic buttons. Add a flyout button and make it hidden. Add a menu section and then add a button, and call the command here. Step#2 : We need to update the JS code, i.e to append...
Read more

Dynamically Populating Ribbon Flyout Menu

Image
I was having a requirement to generate a dynamic ribbon menu under a button i.e. Flyout button menu sections, Here I want to share the steps for achieving this dynamic menu section. I have used Ribbon workbench and some JS scripts. We need to achieve the highlighted menu dynamically. Here in workbench, we need to add a flyout button In the command action, call JS function "populateEnrollmentFlyout" that is responsible for adding the menu sections definition in XML.  Add another command "programClicked"   that will be triggered when the user clicks on the menu section button. Below are the two JS functions used in the above commands. function populateEnrollmentFlyout(commandProperties) { var programsRibbonXml = ""; var command="msd.lead.Command.ProgramClicked"; var programs = retrieveMultiple('msd_programs', "?$select=msd_programid,msd_name"); programsRibbonXml +="<M...
Read more

Upload a file to SharePoint document library using Power automate Flow

Image
I had a requirement to upload a document to the SharePoint document library (integrated with the Account entity in dynamics CE) from the power apps portal, the portal supports uploading and displaying SharePoint documents as documented here ( by placing the document location subgrid on a portal basic/advance form), but our requirement was to allow portal users to upload documents only to specific folders. For achieving this specific requirement, I have used an Html file uploader and a power automate flow that receives the request and creates a file in the SharePoint document library specific folder. The file uploader HTML code snippet, that I have used. The JS code that I used for posting the form-data with "mimeType": "multipart/form-data" , to my power automate flow. Following is the power automate flow that, triggers When a HTTP request is received . For convenience 😋 one can copy the expression below. A successful run output. After a succ...
Read more