Power Nest

  Today, I was facing an error while trying to turn the flows ON in target environment. It was showing following error.   {"code":"FlowMissingConnection","message":"The flow is missing a connection for api 'shared_XXXXXXX'. Reauthenticate the connection or remove from the flow and re-save."}}". Upon further investigation, it has been observed that the flows, having an error while turn ON, were using connections and not connection references. How did it happen? When a flow is created outside of solution, and then subsequently added into the solution, it uses connections instead of connection references. And when this solution is imported into target, it creates a new flow outside of solution irrespective of it being inside the solution. Thus, it should always be a best practice to create flows inside solution as connection references are only supported in solution bound flows. How to identify if a flow is using connections or connecti

Another day, another error while importing managed solution to production. The error suggests that the view (saved query) behind the sub grid which is placed on the form (Form Id) is not present in the solution. " The dependent component SavedQuery (Id="View Id") does not exist. Failure trying to associate it with SystemForm (Id="Form Id") as a dependency.  Missing dependency lookup type = PrimaryKeyLookup. " Here is this can be fixed: Open customization xml in notepad (I recommend notepad++ ) and search with "View Id". Identify the form where this sub grid is placed. Open form -> Open sub grid properties. Set view selector to "Show All Views", save and publish the form. Open the same form again and set view selector to Off, save and publish the form. Now you can export and import the solution again. I will work! How it happened? I believe, when we do customization (place sub grid in this case) on the form from power platform and pu

We often get a requirement to send notification to a user with the record url. User can click on the link and quickly navigate to the record he has been notified about. This requires a dynamic host url (environment specific url) to be pulled out within power automate action. When we use Get row action, we also get an oData url of the record. We can utilize this field to extract host url out of it.

Recently, I was looking to add dynamic url having values coming from the output of some of actions from the top of my power automate to be sent out as teams/email notification.  I was building dynamic url directly in the message section of teams post message action, but for some reason it wasn't working. After that point, I figured out that the html tags with dynamic values does not work directly in the message. To make it work, I have initialize and set variable with the dynamic url and used this variable in the message. This is how the notification received in my teams.

Today, I faced this error on browsing website after web app deployment on Azure and sometimes later, found a fix which has resolved it. We need to enable Directory Browsing on a directory in Microsoft Azure website. To do this, set <diectoryBrowse enabled="true" /> in your web.config. Sample: <configuration> <system.webserver> <directorybrowse enabled="true" showflags="Date,Time,Extension,Size" /> </system.webserver> </configuration> thanks, p.

Hi All, Recently, I came across a requirement where I wanted user to change entity image from html file up-loader. Below is the piece of code used to update entity image.  Uploader.prototype.PostRequest = function (content) { var configurationId = parent.Xrm.Page.data.entity.getId(); var tabConfiguration = { EntityImage: '' }; tabConfiguration.EntityImage = content; //byte[] content of the web resource var jsonContact = JSON.stringify(tabConfiguration); //OData URI var oDataURI = parent.Xrm.Page.context.getClientUrl() + "/XRMServices/2011/OrganizationData.svc/" + "hsl_tabconfigurationSet(guid'" + configurationId + "')"; var req = new XMLHttpRequest(); req.open("POST", encodeURI(oDataURI), false); req.setRequestHeader("Accept", "application/json"); req.