Recently I had a requirement to provide cloning capabilities for one of the projects that I was working on. It wasn’t so simple as to just clone an individual record, but also provide the ability to clone the relationships.
In the second part of the installation of configuration of Azure Logic Apps with the On-Premise Data Gateway, we will review the requirements that are need inside of the Azure Portal. This will cover the creation of the Data Gateway resource, the Logic app and the creation of the Trigger and Action inside of the Logic App designer.
I recently had a requirement to configure Logic Apps for use with the Azure On-Premise Data Gateway and connection to an Oracle On-Premise database. Since I did not have access to the Oracle database at that point, I decided to try this out with an On-Premise SQL Server database as the logic should have been similar. I downloaded the Azure On-Premise Data Gateway and installed it on the server, and the configured the Azure environment to connect to the server and post data back to Dynamics 365.
While working on a project, I recently encountered a strange behavior in Dynamics 365. I am not sure if this is a bug (or feature), but something that we should be really careful about. One of the entities that we were working on, was created without following the organizational guidelines and had to be recreated. In this particular scenario it is not really a big deal because the project is still in early stages of implementation so changes and cleanup occur on a regular basis.
In a few of my recent implementation I had the requirement of making modifications to many child records. Some of these processes required the use of an external SSIS package that executed a console application and ran on a schedule, but more recently I had a requirement to simply deactivate multiple child records. This of course can also be done using cascading rules, but it’s a little more complicated once you involve custom filtering.
In the recent weeks, I have seen a lot of topics in the Dynamics Community forums asking about what are the capabilities of the Dynamics 365 Team Member License, and what actions can or cannot be performed with this license. I have decided to summarize the details from the licensing guide regarding this licenses to be able to answer some of the questions that arise.
Deprecated features are features that Microsoft is planning on removing in a future release of Dynamics 365. The feature will still be available in the current release, which will allow organization the time to prepare and plan on updating their solution before the feature is completely removed.
Our CRM Exchange Sync with support for Microsoft Dynamics 365 has just been released, now with additional functionality and support for additional environments. The CRM Exchange Sync application provides the capability of synchronizing between Microsoft Dynamics CRM Marketing Lists and Contacts with Exchange Distribution Groups, Mail Contacts and Mail User records.
Windows 10 has been released, and Microsoft offered a free upgrade to licensed Windows 7 and Windows 8 users. Windows 10 ships with a new browser called Microsoft Edge, which introduces some great new features and let go of some older capabilities of Internet Explorer. These changes will require CRM to be updated.
On November 1, the Microsoft Dynamics CRM Online December 2012 Service Update was announced.
This update reimagines the ways sales and customer service professionals’ work with CRM. Microsoft is moving away from the traditional data-centric lists and forms approach, and this service update will add new user experiences that simply and visually guide users through their business processes.
