Microsoft has introduced some really nice features with Dynamics 365 (CRM v8.2), but also a bug for business process flows of existing customers created before the December 2016 update. This causes an error message on switching to another business process flow or the completely disappearance of the business process flows from the form.
In separate post l have already blogged on a method to identify and resolve the issue, but from my point of view it is not cloud suitable and not supported for cloud solutions,because these are changes made directly on the database which you wont access to on a cloud solution.
With the new features came also new fields in the system. Unfortunately they haven’t been filled during the update for already existing business process flows. One of them is the required field “unique name” of the “workflow” entity. You can even see it when open the details pane of the new business process flow editor.
You can use a simple query in the advanced find to identify concerned business process flows.
Is just as easy as the identification. Deactivate your business process flow and the system will fill the name automatically and you can activate it again immediately. No code, no sql, just magic but this may not resolve all issues for an on prem solution which mean the database update will help.
Popular posts from this blog
Microsoft in recent months made available a much requested feature by many with the additional way to access read-only data in Microsoft Dataverse. The TDS endpoint for Microsoft Dataverse allows read-only access to Dataverse for reporting and analytics requirements. The Tabular Data Stream (TDS) Protocol endpoint functionality is managed by an administrator with access to the Admin center. This feature becomes a game changer as many Microsoft customers who required this feature and often went down the root of the Data Export Service can now start exploring this capability Prerequisites: To get started using this feature, you will need to ensure that TDS endpoint is enabled as this is required to be able to use this feature via Power BI or SSMS. Sign into the Power Platform Admin Center :( https://admin.powerplatform.microsoft.com/environments ), and then select the appropriate sandbox environment. Note: Its always good practice to test new features in a Sandbox Environment Validate t
Purpose The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item Audience This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments. Pre-Requisites Dynamics 365 with IFD Configuration Dynamics 365 Update 188.8.131.52 (KB4046795) Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later Office 2016 *Recommended, Office 2013 *Compatible Supported browsers for Outlook on the web Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers: Internet Explorer 10, Internet Explorer 11, or Microsoft Edge The following configuration is supported: Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet. Protected Mode
A Colleague from Microsoft shared their Pre go-live checklist that is used in their Fast-Track program. So here is a copy for you all, and what customers must be prepared to answer before Microsoft is deploying the production environment. 1. Solution acceptance by users: UAT A. Is UAT completed successfully? How many users participated in UAT? B. Did UAT test cases cover entire scope of requirements planned for go-live? C. How many bugs/issues from UAT are still open? D. Any of the open bugs/issues a showstopper for go-live? E. Was UAT done using migrated data? 2. Business signoff: A. Business has signed off after UAT that the solution meets business needs? B. Solution adheres to any company/industry specific compliance (where necessary) C. Training is complete D. All features going live are documented, approved and signed off by customer 3. Performance: A.