Power Nest

 Earlier, there was no way to update root business unit since it asks for a parent BU while editing. I tried updating a name from make.powerapps.com, and to my surprise it worked. Go to https://make.powerapps.com Switch to desired environment from top right. Go to Tables Open Business Unit table Click on Edit Edit just a name of a business unit and it will auto save. DONE!!

  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. It will work! How it happened? I believe, when we do customization (place sub grid in this case) on the form from power platform and p...