Starting with Dynamics 365 build number 9.* you must use the XRM Tooling assemblies and the CRMServiceClient instead of the CRMConnection class – see https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/choose-development-style for more information.
First you will need add the nuget package Microsoft.CrmSdk.XrmTooling.CoreAssembly (Core assembly required to develop managed code using the Xrm Tooling Connector)
Afterwards, there are a number of ways that you can instantiate a CRMServiceClient object – see Use CrmServiceClient constructor to connect to Dynamics 365 or Use connection strings in XRM tooling to connect to Dynamics 365
Occasional rantings about Dynamics CRM/365, Power BI and Azure cloud. Taking the first small steps in machine learning, Python and algorithmic trading
Thursday, September 13, 2018
Tuesday, September 11, 2018
Dynamics 365 monthly reading list August 2018
Technical topics (Configuration, customization and extensibility)
- How to configure Dynamics 365 Server to Server (S2S) authentication
- Update SDK tools required to connect to 9.x Dynamics 365 organizations
- Open progress indicator using Xrm.Utility in Dynamics 365 v 9.0
- Walkthrough: execute Azure function from Microsoft Dynamics entity form
- Introduction to Dynamics 365 mobile apps for 9.0 Part 4: new UI components and the CCF
- How to retrieve OData v4 fast in Power BI
- Dynamics 365 Online Deployment tips: set your security group
- Proof of Concept – speech to text notes in Dynamics 365
- Preview feature: integrate Dynamics 365 customer engagement with Microsoft Teams
- Microsoft Business Applications Summit 2018 – sessions on demand
- When data in CRM is updated I want to send it to another application
- Dynamics 365 – drawing activity sequence diagram – display sequence of activities on CRM form using the js-sequence-diagram library
- Dynamics 365 Web API batch request, transaction integration and logic apps
- FTP to Dynamics CRM using Azure functions
- Five ways to improve quality and productivity of Dynamics 365 development
- Advice on improving as a CRM developer
- Getting to know the Dynamics 365 Data Export Service
- When does the plugin registered on setstate message fire in Dynamics 365?
- Enabling feedback for entities
- Delegable or not delegable – things to consider when creating queries in PowerApps
- Turn on soft delete for Azure Blob storage – handy to know in combination with the Attachment management solution
- Thoughts on CRM design and converting user requirements in CRM solutions
- Sample PowerApp: quick capture customer visits into Dynamics 365
- Entity dashboards in the new Dynamics 365 UI
- Dynamics 365 Sales Professional license
- Why you should move to Unified Interface in Dynamics 365 and how to make it happen (Recording Business Applications Summit)
- Common call center metrics for Dynamics 365
- Collaborating for a successful Dynamics 365 project
Labels:
CDS,
CRM,
Customer Engagement,
Dynamics 365,
Dynamics CRM,
microsoft,
msdyn365,
msdyncrm,
PowerApps
Monday, September 10, 2018
Introducing the Dynamics 365 Health Accelerator
The Dynamics 365 Health Accelerator is directly available from the Microsoft AppSource and allows you to rapidly develop healthcare solutions by providing a data model which supports entities based on the Fast Healthcare Interoperability Resources (https://www.hl7.org/fhir/index.html) framework created by HL7. Besides the data model, it also contains pre-built dashboards, workflows, and sample data, as well as other tools to help partners build and deploy new healthcare solutions. The Dynamics 365 Health Accelerator is part of Microsoft’s Industry Accelator initiative which supports industry partners by extending the Common Data Model.
Figure 1. Patient timeline: presentation of clinical information about a patient in chronological order enabling providers to visualize all patient interactions and make informed care decisions
Figure 2. Care Team Visualization: A connected view of the care team associated with a patient and their roles that can be configured to include family and other related relationships
References:
Figure 1. Patient timeline: presentation of clinical information about a patient in chronological order enabling providers to visualize all patient interactions and make informed care decisions
Figure 2. Care Team Visualization: A connected view of the care team associated with a patient and their roles that can be configured to include family and other related relationships
References:
Labels:
CDM,
Dynamics 365,
FIHR,
Healthcare,
HL7,
microsoft,
Vertical
Subscribe to:
Posts (Atom)