One of the biggest issues I have faced with Flows, is when it comes to moving them between environments, and having to re-connect all of the connections, every time. This is a huge chunk of time, especially if you have a lot of actions that use connections in your flows.
This Bookmark-let will allow you to Fix your connections with a click of a button.
Some things to be aware of :
Your actions need to be expanded first, so its a good idea to use this alongside my other Bookmark-let for expanding all the actions. I did think about combining the two, but for the moment, I have kept them separate.
This will pick the first connection in the list. If you multiple connections setup for each type of Action, it will always pick the first one.
Simply drag the below button onto your Bookmarks Bar within Chrome or Firefox, and then when your viewing a Flow, click it to re-connect all of the connections in one go (after you have expanded them)..
Microsoft provide links to download PDF versions of their online documentation. I have created a page with direct links to the main documents, which can be useful for downloading the the latest information for offline viewing.
I recently had a requirement to perform some Data Migration, but I needed a test system while I built up my SSIS process as I didn’t want to use the real online environments. Luckily, I have my own on-premise Dynamics 365 Version 9 Server which I have always used for testing and messing around with solutions and compatibility.
The main issue I have always had with using on-premise servers however is that these days, we are all developing with online environments, and solutions and what not from online cannot be imported into an on-premise environment. In the past, I have often just resorted to hand modifying solutions to get them in to the system. This would often involve editing the solution.xml file within the solution zip file, to alter the version tags at the top, and to remove the crmonline tag. Quite often, this would also require a few modifications to the customizations.xml file to remove any tags that do not exist in version 9 of Dynamics.
Its a hack, but for testing purposes, this was always something that worked.
These days though, you more often than not will face all manor of other issues, such as dependencies on other solutions, and its become a lot harder to achieve this.
Had a curious issue recently where I had set up a new Dynamics 365 Version 9 on premise server for testing. Everything was working as expected until I upgraded to the latest September 2019 release of CRM (update 0.8).
Upon further examination though, it had nothing to do with the update, it was the new Organisation I had created called “Portal”. For some reason, this organisation simply would not work, giving an error when trying to access it. I could see some nasty error messages in the Event Log which made me think it was something to do with the Upgrade (Assembly DLL load issues).
However, I created a new Organisation which actually worked fine.
I think I have come to the conclusion that the name of the org, Portal was producing some internal error with CRM and preventing it from loading. Maybe /Portal in the URL is reserved for something else, who knows.
Its not something that would probably affect many people, but I felt compelled to write a post about it in case anyone else was stuck with this.
This was an interesting find by one of my colleagues, and verified by myself to be a real issue.
All of a sudden, one of our custom entities within our development environment started to throw errors when trying to edit business rules.
We got to the point where we were seriously considering resetting the environment using a backup, when it was discovered that the only thing we could think that had changed was that the entity had been enabled for Entity Images as a test. Sure enough, deleting the field that was created for the entity image was enough to bring the business rules back.
So, let that be a lesson, if you enable entity images on a custom entity, you may just lose access to your business rules.
I am not sure if Microsoft is aware of the issue, or are planning on fixing it, but its something to watch out for.