In today’s business, it’s key to have Unified systems and processes. Often businesses struggle to integrate enterprise data across their ever-growing number of applications and systems, resulting in applications which are meant to help but actually harm productivity.

Disconnected systems often overload employees with much of the painstaking work of searching data, data entry, data processing, and business analysis, and in some cases, data synchronization is manual and the onus of data integrity across systems will fall to employees.

When businesses invest in digital transformation projects to improve efficiency and gain a competitive edge, they have to plan on how new systems and apps will interact with each other. Burdening their employees with the task of manually migrating data between various systems easily counteracts any ROI.

Adoxio's Technical Director of Services Delivery, Colin Vermander will be speaking at eXtreme365 (formerly eXtremeCRM) on March 13-17, 2017, in Lisbon.

The purpose of the eXtreme365 conference is to help the Microsoft Dynamics 365 (CRM) community more effectively grow their business by selling, deploying and extending the Microsoft Dynamics 365 solution. eXtreme365 is dedicated to providing insight to the Microsoft Dynamics 365 future vision and strategy and encourages sharing of knowledge among the Microsoft Dynamics 365 community.  eXtreme supports critical connections with Microsoft, ISVs and partners – all with a goal of helping the community learn, grow and work more productively together.

Colin will be speaking at two sessions: Extend Dynamics 365 Portals with Custom Code, and Everything you need to know - Dynamics 365 Portals Implementations.

We hope to see you in Lisbon!  If you would like to pre-schedule a meeting with Colin while in Lisbon, please feel free to contact us.

With the latest update to Microsoft Dynamics CRM Online 2016 Update 1 (now Dynamics 365) and Microsoft Dynamics CRM 2016 Service Pack 1 (on-premises), Microsoft has increased the maximum allowed attachment size in Microsoft Dynamics CRM Online from its long standing limit of 32 MB to 128 MB (131,072 KB).

This limit increase may come as fantastic news for businesses who require the ability to store large attachments from time to time. This new limit will ensure – in most cases – that larger email attachments coming from your customers will be successfully received, and your business processes aren’t hindered when needing to attach any exceptionally large documents to your opportunities, cases, and service requests.

If you are using CRM portals, this limit increase becomes especially beneficial as customers seeking the convenience of online requests may (occasionally) need to submit a large document that can’t be easily trimmed or broken down into smaller files.

A recent Microsoft CRM Blog article mentioned that the customers using the List Component with SharePoint online must migrate to the server-based integration immediately to avoid disruption of service November 30, 2016 onwards.

Please note that the customers using the List Component with SharePoint on-premises deployment are not affected currently.

To give you some context: Dynamics CRM can be connected with the SharePoint by two different approaches.

1. List Component
2. Server-based Integration

The List Component approach has been deprecated when CRM 2015 Update 1 was announced and the SharePoint integration has to be carried out only with the Server-based Integration approach. However, Starting November 30, 2016, the Sandbox execution for the List Component is scheduled to turn off and this calls for the migration to Server-based Integration even for the existing implementations.

I received this very generic looking message (below) when trying to run a Dynamics CRM portal. After a little experimenting I found the problem to be that my credentials pointed to a user that had not yet been added to the target CRM organization (but did exist in Active Directory).

Yet another reminder to check the basics when faced with strange errors.

The interesting thing here is that the error message I received might lead you to believe that tracing needs to be enabled for your portal (in order to gather more error details). However, this error is actually being delivered from the Dynamics CRM server, and is not reflective of the tracing settings for your portal.

If you are operating Dynamics CRM on premise, and would like it to include these additional exceptional details with its faults (so you can possibly see the reason behind the fault), instructions on how to do so can be found here.

Here’s my original error message: