Tag Archives: Dynamics

Dynamics 365 Monthly Update-November 2017

Quick Links: Featured News | Updates and Releases | Additional News | Training Corner

Featured News

Security Enhancements Announcement for Microsoft Dynamics 365 Government

By default, Microsoft Dynamics 365 Government sets a user session timeout of 8 hours. A user is not required to log in with their credentials for up to 8 hours regardless of whether the user was active or inactive.

With the implementation of the Security enhancements: User session and access management, customers can now set their own session timeout limit for their individual Dynamics 365 instances.

For greater flexibility and better customer experience, Microsoft is moving the maximum session timeout duration from 8 hours to 24 hours. This will allow customers to set a custom session timeout duration between 1 hour and 24 hours.

If the previous 8-hour session timeout duration is required, customers will need to set a custom session timeout for all their Dynamics 365 instances.

Please refer to FedRAMP guidance on recommended inactivity and session timeout parameters for your organization.

Review the highlights of these enhancements in the following video: Security Enhancements: User session management.

Unified Service Desk and TLS 1.2 Mandate for Dynamics 365 (Online)

As part of Microsoft’s ongoing efforts to stay up to date with industry security policies and best practices, the 9.0 update for Dynamics 365 (online) will begin requiring connections for customer engagement applications to utilize TLS 1.2 (or better). The in-market versions of the Unified Service Desk client desktops will be required to have the following registry entries set In order to connect to the CRM online instances running version 9.0:

clip image002 thumb3 Dynamics 365 Monthly Update November 2017

For more information, please review the following articles:

Updates coming to Dynamics 365 Customer Engagement connection security

Microsoft Security Advisory 2960358

Portal Capabilities for Microsoft Dynamics 365 Version Release

Portal capabilities version for Microsoft Dynamics 365 is now available. This release includes an updated portal host and updated solution packages (new solution packages will be available after the portal host upgrades have been completed globally). The portal host will automatically be updated by Microsoft, but action must be taken by your organization to upgrade the solution packages.

Until the solution packages are updated, some enhancements will not be available to portal administrators and/or users. For instructions on how to upgrade the portal solution packages, please refer to this KB article.

New and updated features include:

  • Added a new error message for password confirmation screen when attempting to send email fails due to contact email preference being disabled. Alert emails now provide a link to the Analytics area of the Social Engagement app
  • Resolved issue of deactivated forum threads appearing in the portal
  • Fixed intermittent issue that would not register the website bindings when a new portal is deployed
  • Increased cache performance of knowledge articles in portal

For more information, review the release article.

Go to Top

Updates & Releases

Service Update 5 for Microsoft Dynamics 365 9.0.0 (online)

Service update 5 for Microsoft Dynamics 365 9.0.0 (online) is now available.

This update resolves the following issues:

  • Recipient, and user information is missing in record form when using the Hebrew Language
  • Inactivity script must read IsUSD and USDBrowserMode variables from top window instead of using iframe.
  • Activities are not showing up unless youhover over it in Sales Activity Dashboard using an iOS device.
  • “TypeError: Mscrm.CrmCrossBrowser is undefined” is thrown selecting save after creating rule item in a Record creation, and a rule update.
  • An unexpected error occurs when attempting to enable a Language.
  • A user can download another user’s Report data.
  • Knowledge Base form is throwing an onload error every time the form is loaded.

To determine whether your organization had this update applied, check your Microsoft Dynamics CRM Online version number by clicking the gear icon in the upper-right corner, select About and look for:

Service update 5 for Microsoft Dynamics 365 Online 9.0.0

Service Update 3 for Microsoft Dynamics 365 8.2.2 (online)

Service Update 3 for Microsoft Dynamics 365 8.2.2 (online) is now available.

Some of the issues resolved in this update include:

  • The Regarding field on tracked emails is getting cleared when using App for Outlook.
  • Global workflows are not triggering on Business Process Flow process completion.
  • SLA fields are not displayed in custom entities.
  • When tracking meetings in the Outlook App, the list of participants is not synchronized to Dynamics 365.
  • Unable to hide the tab name in mobile application with Jscript.

For more information about the update, review the following KB article: https://support.microsoft.com/en-us/help/4056116

To determine whether your organization had this update applied, check your Microsoft Dynamics CRM Online version number by clicking the gear icon in the upper-right corner, select About and look for:

Service Update 32 for Microsoft Dynamics 365 8.2.2

Unified Service Desk update 3.1.0

Unified Service Desk update 3.1.0 is now available. The enhancements are primarily focused on aligning with the latest security enhancements in Dynamics CRM online version 9.0:

  • The Unified Service Desk version 3.1.0 supports TLS 1.2 out of the box. This means the client automatically connects to Dynamics 365 9.0 (online).
  • Dynamics 365 9.0 (online) provides capabilities of preventing unauthorized access by supporting inactivity timer and session timer for users. Unified Service Desktop version 3.1.0 provides support for these enhancements, particularly in IE Process hosting type.

For more information, review the Unified Service Desk 3.1.0 is Released blog post.

Dynamics 365 for Field Service and Project Service Automation Update 4

With the goal of continuously improving quality, performance, usability, and responding to some customer feature feedbacks, Microsoft recently released an update for Dynamics 365 for Field Service and Dynamics 365 for Project Service Automation.

Field Service enhancements include:

  • Resolved error message “An item with the same key has already been added” when trying to upgrade from a version 6.0.x.x Field Service build to build
  • Resolved error message “The work order must match the work order set on the booking.” when users attempted to save Purchase Orders
  • Resolved issue of work order forms not displaying in the portal for field service

Project Service Automation enhancements include:

  • Corrected the timestamp for Accounting Date on Project Actuals to show the Approval Date
  • Resolved issue with Project based line window not closing automatically after clicking Save & Close
  • Performance improvements in the Time Entry & Expenses areas

For more details on the update, review this post in the Dynamics 365 Team blog.

Microsoft Social Engagement 2017 Update 1.10

Microsoft Social Engagement 2017 Update 1.10 is now available.

New and updated features include:

  • Updated user experience for activity maps
  • Alert emails now provide a link to the Analytics area of the Social Engagement app
  • New training video on Microsoft Virtual Academy
  • New social post packs

Enhancements include:

  • Improvements on the backend for acquisition stability and reliability
  • Resolved an issue with truncated text strings in previous Social Engagement versions
  • Resolved an issue with keyword filters where the input field was limited

For more information, review the What’s new in Microsoft Social Engagement 2017 Update 1.10 article in the Dynamics 365 Team blog.

Deprecation of post.profile.id object in Social Engagement JSON payload

Social Engagement includes a feature that allows users to send posts to Azure Event Hubs by using Automation Rules in Social Engagement. The post content is sent in the form of a JSON object that contains the content of a post and its metadata.

As part of evolving functionality, Social Engagement is updating the JSON payload by replacing the post.profile.id field with a new post.profile.uri field.

The reason for the change is that the current implementation of the post.profile.id field is not source-specific. Consequently, the profiles of two authors with the same profile name on different platforms might end up having the same profile.id. Moving forward, post.profile.uri will also include a source-based identifier as part of the field value (for example: mse-tw://#12345678).

For more information on the impact of the this change and the timeline, please review this blog post on the Microsoft Dynamics 365 Team blog.

Go to Top

Additional News

Sales & Marketing: New Dynamics 365 integrations across Adobe Experience Cloud

Microsoft and Adobe established a strategic partnership in an effort to help equip businesses to better respond to their customers in a digital environment. The joint efforts are are allowing enterprises to transform their customer experiences, and drive more efficient business processes. We are pleased to announce that the offering from the partnership: Dynamics 365 is now integrated with Adobe Experience Manager, Adobe’s industry leading content management solution in the Adobe Marketing Cloud. Available to both Microsoft and Adobe customers, this integration will help organizations optimize enterprise sales and lead management.

This integration will help solve some of the complex challenges such as:

  • Audience: Helping organizations move from a disparate view of customers and poor segmentation, to a more holistic view with intelligent segmentation.
  • Workflow: Shifting from teams using multiple systems and processes for customer engagement, to integrated systems and a unified view that empowers actions, collaboration and productivity.
  • Personalization: Transitioning from manual process for defining and delivering customer experiences to data driven and automated content personalization.

Review the announcement here.

Build a redist folder to install Dynamics CRM 2016 without an internet connection

Several customers have requested an updated PowerShell script that can download the Dynamics 2016 pre-requisites and put them in a folder for installations without internet access. An updated script is now available.

Typically, PowerShell scripts are provided as a downloadable PS1 file, but for this version, the text and a txt download have been provided for review in the Dynamics CRM in the Field blog:


Security Compliance and Regulatory Requirements

Microsoft publishes compliance guides and trust and transparency guides on the Service Trust Portal to demonstrate compliance with global standards and regulations and to provide customers with information on how we manage our cloud services and protect customer data. The Service Trust Portal includes a Compliance Manager application that can be launched to control management, integrated task assignment, evidence collection, and audit-ready reporting tools to streamline your compliance workflow.

The Service Trust Portal and Compliance Manager is currently in Preview and we need your feedback to make it as useful to you as possible. Have a comment or suggestion? Please use the Feedback button in the Service Trust Portal and tell us what you think.

The Microsoft Trust Center is an important part of the Microsoft Trusted Cloud initiative and provides support and resources for the legal and compliance community. It is an excellent resource for customers to learn how Microsoft implements and supports security, privacy, compliance, transparency in all our cloud products and services. For more information:


Report a Computer Security Vulnerability

The Microsoft Security Response Center investigates all reports of security vulnerabilities affecting Microsoft products and services. If a customer believes they have found a security vulnerability in a Microsoft product, then they are asked to report it and Microsoft will work with them to investigate it.

Please note: The Microsoft Security Response Center does not provide technical support for Microsoft products.

If you believe you have found an issue that meets the definition of a security vulnerability and is not resolved by the 10 Immutable Laws of Security, please send an e-mail to secure@microsoft.com. To help us better understand the nature and scope of the possible issue, please include as much of the below information as possible:

  • Type of issue (buffer overflow, SQL injection, cross-site scripting, etc.)
  • Product and version that contains the bug, or URL if for an online service
  • Service packs, security updates, or other updates for the product you have installed
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue on a fresh install
  • Proof-of-concept or exploit code
  • Impact of the issue, including how an attacker could exploit the issue

For more information, review this bulletin in the Security TechCenter.

Important changes coming in Dynamics 365 Customer Engagement

Microsoft provides announcements on features that will be deprecated from the Dynamics 365 Customer Engagement capabilities to assist Administrators and IT professionals with future planning and releases. “Deprecated” means Microsoft intends to remove the feature or capability from a future major release. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few years. After removal, the feature or capability will no longer work.

To see the list of current and past announcements, please review the Important Changes article on the Dynamics 365 Documentation site.

Go to Top

Training Corner

New Customer Engagement Developer Documentation for 9.0

With the release of Dynamics 365 (online) version 9.0, there are some changes coming with the developer documentation:

The SDK is a combination of documentation and resources that developers use to build software. Until now, we were using the term “SDK” to refer to the developer documentation for Dynamics 365 Customer Engagement and for the download package containing assemblies, tools, and the offline version of the documentation. To clear up this confusion and to be consistent with the terms we use for all our documentation, we will now refer to the developer documentation as the Developer Guide.

In addition to the name change, customers will now be able to download the individual documentation, tools and sample code as needed rather than the entire package. The client scripting or client API has also been restructured to allow for better search results for individual APIs by providing dedicated pages for each and the entity metadata is being leveraged to generate reference documentation for most entities in the system together with a complete list of all the properties, attributes and relationships.

Take a look at What’s new for Customer Engagement developer documentation in version 9.0 for more information on this update.

Is Dynamics 365 Server-Side Sync filling up your database?

Dynamics CRM Server-Side Sync allows customers to capture logs which can aide in troubleshooting issues with user mailboxes. The alerts are shown on the alerts wall or the alerts section in the mailbox or email server profile records. If all the errors, information and warnings are being captured, then it can appear as though server-side sync is filling up the TraceLogBase table.

Customers have the option to remove the information they don’t want to capture from the database by creating a bulk delete job:

  1. Login to Dynamics CRM Application as an administrator, then navigate to
    Settings >Data Management

clip image0042 Dynamics 365 Monthly Update November 2017

  1. Click Bulk Record Deletion

clip image0061 Dynamics 365 Monthly Update November 2017

  1. Click the New button to create a new job, then click Next in the Bulk Deletion Wizard. In the Define Search Criteria window, select Traces in the Look for drop down.

clip image008 Dynamics 365 Monthly Update November 2017

  1. Select Level then click Enter Value: Level

clip image010 thumb1 Dynamics 365 Monthly Update November 2017

  1. Choose the values you want to delete, then click OK

clip image012 Dynamics 365 Monthly Update November 2017

  1. Identify Server Side Sync for Regarding and then choose the Regarding Object Type. Continue through the wizard to finish creating the bulk deletion system job.

clip image014 Dynamics 365 Monthly Update November 2017

For more information, review this post on the CRM in the Field blog.

Customer Engagement Technical Journey Offering

Microsoft is pleased to announce the newly updated Customer Engagement technical journey is now available online, with the addition of seven new technical training webcasts. This resource is primarily available for Partners, but customers can access some of the information in the Microsoft Partner Network Support page.

The Technical webcasts are available for Partners, but Customers can also join them as Guests. Sessions are being offered in the Americas, Asia Pacific and EMEA with some beginning in December 2017:

Please note: Additional dates and languages will continuously be added throughout FY18; please check back frequently.

New Training Courses: Microsoft Dynamics Learning Portal

New Field Service courses are available in the Microsoft Dynamics Learning Portal:



Agreements, Inventory, and Purchasing


Mobile and Dispatch


Setup and configuration


Field Service Assessment


Field Service exam MB2-877 (available December 2017)


Ideas for Microsoft Dynamics 365

Help us improve Microsoft Dynamics 365 and its family of products and solutions by discussing ideas, providing suggestions, and giving feedback. Use the forums listed on the Ideas page to share your thoughts. Search through the existing ideas, before suggesting a new one, and you can vote on them to help increase visibility.

Go to Top

Let’s block ads! (Why?)

Dynamics CRM in the Field

Cloud, Edge, or Local? Dynamics 365 Finance and Operations Deployment Options

Feature 300x225 Cloud, Edge, or Local? Dynamics 365 Finance and Operations Deployment Options

In today’s blog on Dynamics 365 for Finance and Operations, we are going to touch on different deployment scenarios that are available for customers. When choosing a Microsoft Dynamics 365 for Finance and Operations deployment, there are three options: Cloud, Cloud and Edge (hybrid), or Local Business Data (on-premises).

The option you choose will depend on your business need. One great feature is that you have the option to change up your deployment down the line. Why would you do that? Well, maybe you recently made a large infrastructure investment but still want to implement Dynamics 365. You could start with a Local implementation and then switch over to the Cloud at the end of that hardware’s life cycle. How great is that?

Now let’s move on to learning more about each of the deployment options (we’ll use Microsoft’s descriptions of each type and explain what they mean).


This scenario offers a fully Microsoft managed cloud ERP service that includes high availability (H/A), disaster recovery (D/R), sandbox environments, and application life cycle management that are combined with cloud-based systems of intelligence, infrastructure, compute, and database services in a single offering.

What does this mean?

It means that your Dynamics 365 deployment lives in Microsoft’s Cloud and is fully managed by them, so Microsoft is the Data Trustee in this scenario. This covers your high availability and disaster recovery using geo-redundant data centers. This option has the tightest integration with the Azure stack offerings like BI, Machine Learning, Logic Apps, etc. Microsoft is taking a Cloud first approach so some new functionality around infrastructure tie ins (SQL) will likely appear here first.

Why would you consider this deployment type?
There are some great benefits with this option. You get “always on” infrastructure without having to staff it and you get the disaster recovery (D/R) and high availability (H/A) without the additional hardware investments. One of the biggest advantages of this option is scalability. You can scale up when needed and without an additional hardware investment. You are paying for user licensing and not the computing power or “hardware.” Need to add a new division and need additional AOS resources or SQL processing power? You can scale up with a service request.

Cloud and Edge

A primarily cloud-based scenario that combines the power of a Microsoft managed Cloud service with plans to enable organizations to run their business processes from application servers at the edges. This means that transactions are supported by local application services and business data is stored locally.

What does this mean?

It means that this is a hybrid of Cloud and On-Premises deployments. Transactions are entered via local applications and the data is stored locally in the customer’s data center. There is also a central Cloud node which provides a single view of the business data and provides failover to the Cloud – D/R and H/A. Since it is still using the Cloud, you can still take advantage of BI, Machine Learning, etc. without a lot of manual configuration.

Why would you consider this deployment type?

Some organizations, like Retail or Manufacturing, may require things to be local for business continuity. For example, a retailer must be able to run the store POS operations even if internet connectivity goes down for a few seconds or minutes. This way you can capture the transactions locally and sync back up when you’re back online and don’t have to worry about redundant internet connectivity at the store level. In this scenario, both the customer and Microsoft are considered the data trustee.

Local Business Data

A scenario that will allow customers to deploy a Dynamics 365 for Finance and Operations environment into their or their partner’s data center and run operations without replicating business data to the Cloud.

What does this mean?

This one is fairly self-explanatory. The customer deploys all the Dynamics 365 components in their own data center. None of the applications or data reside in the Cloud. The customer is the data trustee, responsible for H/A and D/R, and for maintaining all the servers in the data center. Since there isn’t integration to the Cloud, options for things like integrated BI and Machine Learning are not available or require some additional configuration. Configuring all applications does require some heavy lifting from your IT staff and there are some serious system requirements.

Why would you consider this deployment type?

Some organizations are just not ready or comfortable with their mission critical data and apps residing in the Cloud. Or maybe you just spent a ton of money on recent hardware improvements and want to take advantage of that. Some industry mandates may require full access and control to the infrastructure or data. Maybe internet connectivity is an issue and there aren’t many options for redundant connections.

Here is a matrix that outlines the options and provides some details on each. Please note that the image is now a bit out dated and all the options are currently available.

121117 2220 CloudEdgeor1 Cloud, Edge, or Local? Dynamics 365 Finance and Operations Deployment Options

Clearly, there is a lot of to consider when making your decisions on a Dynamics 365 for Finance and Operations deployment type. The good news is that there are options and you can choose to go one route in the beginning and then change directions downstream if you want!

Learn more about Dynamics 365 for Finance and Operations in our on-demand webinar series! Learn how PowerObjects can help you on your Dynamics 365 journey here.

Happy Dynamics 365’ing!

Let’s block ads! (Why?)

PowerObjects- Bringing Focus to Dynamics CRM

13 Features Being Removed From Future Releases of Dynamics 365

Normally we hear about all the great new features being added to Microsoft Dynamics 365. But you also need to be aware of the features and capabilities that are being deprecated

Technically “to deprecate” means “to express disapproval of (something)”. In the software world, it means something that is “usable but regarded as obsolete and best avoided, typically because it has been superseded.”

According to Microsoft deprecated means “we intend to remove the feature or capability from a future major release of Dynamics 365.” However, the feature or capability will continue to work and is fully supported until it is officially removed.

It is important for all Dynamics 365 users to be aware of which features are on the chopping block so that they can determine if it will impact their business and decide on the best strategy before their next upgrade.

In this article, Microsoft discusses 13 deprecated features that apply to Dynamics 365 Customer Engagement as of version 9. Customer Engagement refers to the applications that make up the CRM portion of Dynamics 365: Sales, Customer Service, Field Service, and Project Service Automation applications.

Deprecated Features:

  1. Service scheduling in Dynamics 365 for Customer Service
  2. Dialogs
  3. Parature knowledgebase as the Dynamics 365 knowledge management solution
  4. Project Service Finder app
  5. Contracts, Contract Line Items, and Contract Templates entities
  6. Standard SLAs in Dynamics 365 for Customer Service
  7. Relationship Roles
  8. Mail Merge
  9. Announcements
  10. Ready-to-use business processes available through Add Ready to Use Business Processes setting
  11. Some client APIs
  12. EntityMetadata.IsInteractionCentricEnabled property
  13. Silverlight (XAP) web resource

When the Crowe CRM team looked at this list, we spotted  a few we felt would be most likely to impact our Dynamics CRM and Dynamics 365 clients during their next upgrades and would require additional planning.

  • Service Contracts – plan to migrate Contracts to Entitlements.
  • Relationships – plan to migrate Relationships to Connections.
  • Outlook Client – plan to migrate to new Outlook App including meeting the server side requirements.
  • Mail merge – change document templates.
  • Service scheduling – move to Field Service.

But it’s not all bad news. Microsoft is continually adding new functionality.  Two new features that our team is excited about are:

  • Advanced find: Advanced find now has the option to build a NOT IN query. For example, users can query for all cases that do not have a related task.
  • MultiSelect option set: Users who customize forms can now add multi-select fields to forms, quick view and quick create forms and read-only and editable grids.

These new features may sound simple, but they will be huge time savers for some organizations.

Next Steps

When features are removed, it is usually because there is now a better way to accomplish the same result. Microsoft gives recommendations for the functionally set to replace anything that is being deprecated. Working with a knowledgeable Microsoft Dynamics 365 partner, such as Crowe Horwath, means this planning will be done before your next upgrade.

If you are interested in discussing an upgrade plan for Microsoft Dynamics 365 (formerly Microsoft Dynamics CRM) contact us today.

Check out our offer on AppSource “Moving CRM to Dynamics 365: 3-Hr Assessment” if you are interested in moving to the Dynamics 365 cloud.

By Ryan Plourde, Crowe Horwath, a Microsoft Dynamics 365 Gold Partner www.CroweCRM.com

Follow us on Twitter: @CroweCRM

Let’s block ads! (Why?)

CRM Software Blog | Dynamics 365

Microsoft Dynamics 365 vs. SalesForce

Trying to decide whether to implement Microsoft Dynamics CRM or SalesForce may seem like a tricky decision at first. We are here to guide you through your decision-making process and present some advice our clients have found helpful in the past.

Logan Consulting is a proud supporter of Dynamics CRM, also known as Dynamics 365, for a variety of reasons. Dynamics 365’s overall cost, integration ability, development, deployment, and consulting options outshine the competitors.

Here’s why:

Let’s block ads! (Why?)

CRM Software Blog | Dynamics 365

How to Solve Lookup Filtering Issue with Dynamics 365 version

The October 2017 Dynamics 365 Service Update 1 for 8.2.2 delivers a load of updates and hotfixes for Dynamics 365 Online Instances. Recently, one of our clients noticed that with this update, some of their Lookup filtering on related records was no filtering correctly. Upon investigation, this issue seems to only occur with fields that are being filtered by a lookup, which is located in the header of the form. If you are unsure of whether this will affect your system you can check your version number by clicking on the cog icon in the top right and then clicking on ‘About’.

image thumb How to Solve Lookup Filtering Issue with Dynamics 365 version

As mentioned earlier, the issue occurs when a lookup field is being filtered by another lookup field located in the header. The screenshot below shows the customization, where the lookup values of the Contact field should be filtered by the lookup value of the Account field when an Account is selected on an opportunity. Unfortunately, this filtering does not occur and the User is presented with a full list of Contacts in Dynamics 365.

image thumb 1 How to Solve Lookup Filtering Issue with Dynamics 365 version

image thumb 2 How to Solve Lookup Filtering Issue with Dynamics 365 version

A simple way to fix this would be to also put the field of the related record on the main form as a hidden field. The screenshot below shows that I have added the lookup field located in the header on the form as well and have set it to be hidden. This will allow you to keep the lookup in the header while also maintaining the filtering.

image thumb 3 How to Solve Lookup Filtering Issue with Dynamics 365 version

Let’s block ads! (Why?)

Magnetism Solutions Dynamics CRM Blog

Incredible offer for Dynamics SharePoint Organizer (SPO) users

With Dynamics SharePoint Organizer (SPO) each CRM entity is configured how the entity integrates with the corresponding SharePoint Document Library. Naturally, each CRM entity has different type of documents and different tags (metadata) that describes the type and content of the document, what the document is about, and how it relates to other documents and other related parties in and outside the organization. When document is generated in CRM entity, it is linked to a record as attachment to Notes, and as attachment to Email activity. The record has attributes / fields to describe the record and documents related to it. A record of an Invoice entity has the Invoice document attached to Notes or attached to incoming Email sent from the accounting department. The record has fields that describe the Invoice document such as invoice number, total amount, due date, invoice description, and the Account that was issued with this invoice. When invoice document is uploaded to SharePoint, the SharePoint columns are updated with these fields, which are called metadata. Metadata is crucial to filter documents in a Document Library View, and improve the relevance of SharePoint search results.

One entity may have many documents, and the documents can be grouped into Document Types. As an example, an organization managing projects with customised entity Projects, may have documents of the types: Project SOW, Project Milestones, Invoices, and Payments. SharePoint document library is configured to accept these four types of documents, created in the Project Entity in CRM. Dynamics SPO can be configured, for the Project Entity, to match the document in CRM with the corresponding Document Type in SharePoint. Categorizing documents by their types enhance SharePoint navigation. The corresponding projects document library stores all project’s documents in one library, and displays the list of documents based on selected document type.

Dynamics SPO can configure the SharePoint folder structure where documents are uploaded. There are 3 different approaches to SharePoint folders structure:

Single Folder Structure – in this configuration all documents related to an entity are uploaded into a selected folder. Each entity can be configured to upload to a related folder in SharePoint, Orders are uploaded to a folder called Orders, Invoices to Invoice Folder, and Payments to the Payments folder.

Alternatively, two or more entities are configured to upload to one selected folder, let’s say “Commercial” folder. In this case Orders, Invoices, and Payments documents are all uploaded to “Commercial” folder. Note that in addition to selecting the folder to upload the documents, tagging them with Document Types like Orders, Invoices, and payments, will filter the required documents, although all documents are in one single folder.

Child / Parent Folder structure – When two CRM entities are related to each other, like Invoices are related to Accounts, Dynamics SPO will create new folder when an invoice is uploaded for an Account folder not yet created in SharePoint. In this structure it firstly lists all Accounts as folder names, the Parent Folder and when a folder of an Account is opened, the documents of this account are listed in the Child Folder.

CRM Out Of Box Structure –   The third option in Dynamics SPO is for customers already using CRM out-of-box (OOB) integration with SharePoint, and wishing to keep the existing folder structure which already is in use to upload documents to SharePoint. While Dynamics SPO will follow the CRM OOB integration with SharePoint, other features like Document types and metadata are available even for those existing folders.

No doubt that using SPO functionality to upload documents to SharePoint is far more efficient and time saving than the one offered with CRM OOB integration with SharePoint.

  1. Users can automatically upload documents with Workflow
  2. User can upload multiple selected documents directly from Notes and from Emails in one go. With the OOB integration you can upload one document at a time, and only after it is saved to hard disk
  3. Upload file Zipped with many documents or unzip on the fly when zip file is selected to upload to SharePoint.

Incredible offer for Dynamics SharePoint Organizer (SPO) users

For limited time only, customers purchasing Dynamics SPO will receive FREE online hand on training configuring any 2 CRM entities to upload documents to SharePoint. Dynamics SPO is available to download as trial version. We provide unlimited 30 day extended trial periods, and FREE email support and advice on best practises configuring Dynamics SPO for your organization.

Click here to Download Trial Version

Let’s block ads! (Why?)

CRM Software Blog | Dynamics 365

How to Create a Relationship with Long Schema Names in Dynamics 365

When dealing with a system that involves many complex entities, we’re bound to have long entity names in Microsoft Dynamics 365. Longer entity names could be to further modularise separate functionality in the system without compromising the descriptiveness of the entity name. For example, you can have two entities in CRM managing an Analytical Dashboard website called “Analytical Dashboard User Settings” and “Analytical Dashboard Entity Settings”. This could be a problem when we want to create relationships between these two entities that have long schema names. This blog will demonstrate on how you can work around an existing out-of-the-box limitation given the assumption that you do not want to alter with Dynamics 365’s schema name generation conventions (will expand below).

To demonstrate this, I’ve created two custom entities with the given names above. Dynamics 365 will autogenerate the following schema names appropriately.

image thumb How to Create a Relationship with Long Schema Names in Dynamics 365

The out-of-the-box behaviour of creating relationships via create new 1:N Relationship record in Dynamics 365 is when you create a relationship from the Primary Entity e.g. Contact, and you need to set the Related Entity. Once we set the Related Entity e.g. Account, CRM would automatically generate the schema name of the relationship. The autogenerated schema name is a concatenation of the Primary Entity schema name and the Related Entity schema name.

image thumb 1 How to Create a Relationship with Long Schema Names in Dynamics 365

I will create a new 1:N Relationship from Primary Entity “Analytical Dashboard Entity Setting” to Related Entity “Analytical Dashboard User Setting”. When we create the 1:N Relationship record from “Analytical Dashboard Entity Setting” and set “Analytical Dashboard User Setting” as the Related Entity, the relationship schema name is autogenerated but appears to be incomplete.

image thumb 3 How to Create a Relationship with Long Schema Names in Dynamics 365

It’s evident that there is a 41 character limit for the relationship schema name field. This can be a nuisance, especially for someone like me who sticks to schema naming conventions based on how the system autogenerates and concatenates schema names.

The workaround to this underlying out-of-the-box behaviour is through creating a relationship via creating a lookup field. Creating a lookup field from the Related Entity (since lookup fields refer to the Primary/ Parent Entity) allows us to work around the character limit issue for the relationship schema name field. Creating a lookup field automatically creates a Relationship record between the Primary and Related Entity.

If we want to create a relationship via lookup field between Primary Entity = Contact and Related Entity = Account, we need to make a lookup field from Account, and set the Target Record Type (which is the Primary Entity) to Contact. Default CRM behaviour does the same automatic generation of naming fields with the addition of also concatenating the schema name of the lookup field (in the screenshot, this is the field schema name “Primary Contact”).

image thumb 4 How to Create a Relationship with Long Schema Names in Dynamics 365

Now we can create our relationship for our entities with long schema names accordingly through this method. I’ve created the lookup field for the Related Entity “Analytical Dashboard User Setting”, set the Target Record Type to the Primary Entity “Analytical Dashboard Entity Setting”.

image thumb 5 How to Create a Relationship with Long Schema Names in Dynamics 365

This time, the autogenerated relationship name returns what we would expect – no incomplete names when both schema names are concatenated. The generated relationship schema name “mig_analyticaldashboardentitysetting_mig_analyticaldashboardusersetting_MainEntitySetting” also includes the lookup field schema name “MainEntitySetting” which we can remove.
We can assess the relationship schema name further by checking the 1:N Relationship record that automatically gets created by the system. The character limit of entering the relationship schema name manually gets ignored as the field gets populated based on our created lookup field. Thus, we are able to have our intended relationship schema name between our two entities without compromising naming conventions. 

image thumb 6 How to Create a Relationship with Long Schema Names in Dynamics 365

Do note that the when creating the lookup field, a prefix will be added to the schema name by default. It is recommended to delete the leading prefix on the Relationship Name field when creating your lookup field e.g. ‘mig_’ in the autogenerated relationship name. This is to avoid having a double prefix name on the final product as shown in the screenshot above e.g. ‘mig_mig_ …’

Let’s block ads! (Why?)

Magnetism Solutions Dynamics CRM Blog

9 Ways Microsoft Dynamics CRM nurses Healthcare Provision to its full potential

With flu season in full swing, healthcare is at the top of everyone’s mind. Whether you’re a patient or a healthcare provider, there is no illusion that the healthcare system is perfect. Certain things can be streamlined and made more efficient, helping everyone involved.

Enterprise Resource Planning (ERP) solutions are a logical group to turn to in search for a remedy (yes – medical humor will be involved). But we’re here to make the case that Microsoft Dynamics CRM is an all-round ERP winner when it comes to healthcare.

Here are 9 ways that CRM can improve the quality of services of a healthcare provider.

  1. Patient history access

Avoid the all-time irritating experience of asking “So why are you here?” and having a patient stare back at you with dismay as they have to repeat their ‘journey’ for the fifth time. Microsoft Dynamics CRM allows access to a centralized patient profile with a list of previous appointments and referrals. You can now spend that time focusing on more targeted questions.

  1. Targeted educational outreach

You effortlessly improve the overall health of patients with automated messaging campaigns. For example, you can make sure your Diabetes patients receive newsletters with tips, or your Smokers are alerted to group meetings to help them quit. Something so simple and easy can lead to some results.

  1. Remote monitoring

Patients confined to their homes are always difficult to treat; you may not get there in time of an emergency, or spend a long time commuting away from other patients. Microsoft Dynamics CRM allows you to monitor at-home medical devices as well as receive alerts when vitals, etc. start to misbehave or fall into dangerous zones. Response time can this be heavily shortened.

  1. Patient profiles – not your average EHR

Say ¡adiós! to symptom-listing EHRs. Microsoft Dynamics CRM allows for the creation of a patient profile, which includes lifestyle choices among other useful details. These profiles are important because studies have shown that the quality of healthcare provided is not the only thing affecting patient health. When doctors are aware of these other factors, they can better tailor their treatment and healthcare plans.

  1. Building care plans

With all the patient data that a CRM can hold, it easily builds unique care plans that tailored to a specific patient’s requirements and needs. Additionally, it allocates tasks to each member on a care team. Coupled together, these make a patient’s treatment more effective and efficient.

  1. Better coordination and communication

Furthermore, Microsoft Dynamics CRM provides a platform for communication: the patient and all healthcare providers involved are updated with new tasks, notified to missing treatments, and can communicate in real-time. More efficient care and fewer mistakes are just a few of the positive outcomes of CRMs in the healthcare industry.

  1. Cohort analysis

Furthermore, this comprehensive conglomeration of data enables a number of insights to be drawn, not solely based on the analysis of a single patient, but on a whole population. This is a slightly harder point to describe, but analysis → insight → better action/diagnosis/treatment is the overall gist.

  1. Clinical trial management

Again, not an expert in the goings-on of a clinical trial, but Microsoft Dynamics CRM is noted to be able to streamline the entire process. From planning and implementation to tracking and analysis, data is centralized and easily accessible and manageable.

  1. Recruitment aides

Microsoft Dynamics CRM is also equipped with recruitment tools to assist in the hiring of highly qualified medical professionals. Ultimately, this can only help maintain a level of quality healthcare provision, if not improve it too.

Even if you just read the section headers, you can see that there are many benefits to adopting Microsoft Dynamics CRM if you’re a healthcare provider.

Want to find out more or a get a personalized demo – contact us.

John Hoyt, Technology Management Concepts, www.abouttmc.com

Let’s block ads! (Why?)

CRM Software Blog | Dynamics 365

How to Fix Invalid User Authorization Error in Dynamics 365 Upgraded Workflows

Recently, we upgraded a client’s CRM 2011 to Dynamics 365. In CRM 2011 instance, there were some workflows that were using custom workflow activities. However, after the upgrade, we were getting an error in Dynamics 365 saying, “Invalid User Authorization – The user authentication passed to the platform is not valid”.

image thumb How to Fix Invalid User Authorization Error in Dynamics 365 Upgraded Workflows

I was getting this error when I tried to open the workflows that were using the custom workflow steps, and when I tried to activate a draft workflow process.

I did some research on this issue. I couldn’t find the exact cause of this issue, and it turns out I am not the only one affected by this issue. But what I did find was a workaround for this issue. In this blog, I will walk through the steps that helped me to overcome this issue.

  1. Create a backup solution of the all the workflows.
  2. After the backup solution has been exported, delete the workflows that are using custom workflow activities.
  3. Unregister the custom workflow activities that were added during CRM 2011 to Dynamics 365 upgrade.
  4. Register those workflow activities again.
  5. Import the backup solution of the workflows that was exported earlier (at step 2).

And this is it, but be sure to test the workflows. The solution above is just a workaround, but I am not a 100% sure what causes this error, and how it can be prevented.

Let’s block ads! (Why?)

Magnetism Solutions Dynamics CRM Blog

D365 In Focus: Field Service for Dynamics 365 from D365 University [VIDEO]

D365 In Focus Field Service Course Still 800x600 300x225 D365 In Focus: Field Service for Dynamics 365 from D365 University [VIDEO]

Dynamics 365 for Field Service is used by organizations to have better visibility and control of their resources, such as technicians, or equipment that they use for service calls. In this episode of Dynamics 365 In Focus, D365 University Trainer, Tad, will take you through the top reasons why your organization would benefit by taking our Dynamics 365 for Field Service training course. For more information about this course, register for our live PO TV webcast for a preview of the content, and then check out our D365 University page to see when the course is available.

Let’s block ads! (Why?)

PowerObjects- Bringing Focus to Dynamics CRM