New Changes / Deprecated Archives - Microsoft Dynamics 365 Blog http://microsoftdynamics.in/category/microsoft-dynamics-365/new-changes-deprecated/ Microsoft Dynamics CRM . Microsoft Power Platform Tue, 29 Sep 2020 14:41:16 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.5 https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/04/cropped-Microsoftdynamics365-blogs.png?fit=32%2C32 New Changes / Deprecated Archives - Microsoft Dynamics 365 Blog http://microsoftdynamics.in/category/microsoft-dynamics-365/new-changes-deprecated/ 32 32 176351444 Enable Queue or lead entity in TO or Form Field of Email of Sales up and customer service Hub – lead entity is not visible under email TO and From Field http://microsoftdynamics.in/2020/09/29/enable-queue-or-lead-entity-in-to-or-form-field-of-email-of-sales-up-and-customer-service-hub-lead-entity-is-not-visible-under-email-to-and-from-field/ Tue, 29 Sep 2020 14:41:16 +0000 http://microsoftdynamics.in/?p=4188 As we can see in the above screenshot when we open an email from Sales Hub it doesn't search for Queue record in TO or FROM fields and the same way if we open an email from Customer Service Hub it won't search  Lead record.

As we know in Legacy Web client there was no setting available to include or exclude them except Javascript so it took us some time to accept there might be some configuration or setting we might be missing. and with some research, my college provided the information providing below community query and it was helpful. thanks to Clofly Mao

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/361316/how-to-enable-the-email-from-field-to-include-queues-as-a-selection

So we can follow the below steps to add or remove entities from Model-Driven apps to show or hide them from Email entity but remember these are not only limited to Emails, if you remove any entity it will be removed from whole model-driven app.

Go to
https://dvmske.crm8.dynamics.com/main.aspx?forceUCI=0&pagetype=apps
and open app designer or best practice is to create a solution add your model-driven app to it and then edit the same.

The post Enable Queue or lead entity in TO or Form Field of Email of Sales up and customer service Hub – lead entity is not visible under email TO and From Field appeared first on Microsoft Dynamics 365 Blog.

]]>

At First Glance, this looks like some kind of bug that in Customer service hub To field Contain different entity from Sales Hub as in the Legacy Web Client there was no option to configure TO or FROM field Entities without JS.

But in UCI you can add or remove the entity from TO or FROM "Party field" of Email but sacrificing howl entity from the HUB.

https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/09/entity-missing-from-email-party-fields.png?fit=1931%2C1165

As we can see in the above screenshot when we open an email from Sales Hub it doesn’t search for Queue record in TO or FROM fields and the same way if we open an email from Customer Service Hub it won’t search  Lead record.

As we know in Legacy Web client there was no setting available to include or exclude them except Javascript so it took us some time to accept there might be some configuration or setting we might be missing. and with some research, my college provided the information providing below community query and it was helpful. thanks to Clofly Mao

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/361316/how-to-enable-the-email-from-field-to-include-queues-as-a-selection

So we can follow the below steps to add or remove entities from Model-Driven apps to show or hide them from Email entity but remember these are not only limited to Emails, if you remove any entity it will be removed from whole model-driven app.

  1. Go to
    https://dvmske.crm8.dynamics.com/main.aspx?forceUCI=0&pagetype=apps
    and open app designer or best practice is to create a solution add your model-driven app to it and then edit the same.

  2. Click on Entities which will open up a list of entities checked means added to the app

  3.  Search for the entity missing

  4. Check the entity and then scroll from Entity View to add forms or view to be available on the hub

  5. Save and Publish

Same Way we can add lead fro the Customer Service hub and now Both entities will be visible in TO fields of the email.

The post Enable Queue or lead entity in TO or Form Field of Email of Sales up and customer service Hub – lead entity is not visible under email TO and From Field appeared first on Microsoft Dynamics 365 Blog.

]]>
4188
Migration to UCI : Ribbon button not visible / Hidden , Debug Entity Ribbon application command bar using command checker http://microsoftdynamics.in/2020/09/18/migration-to-uci-ribbon-button-not-visible-hidden-debug-entity-ribbon-application-command-bar-using-command-checker/ Fri, 18 Sep 2020 16:37:11 +0000 http://microsoftdynamics.in/?p=4167 There is a new command available in UCI to help us troubleshoot the ribbon, It will show Button Properties, Command Properties like Action, Enable Rule, Display rule, and the best part is we don't have to install any tool or enable anything.

We just need to add these parameters in the entity "&flags=FCB.CommandChecker=true&ribbondebug=true"

It can be an entity

https://dvmske.crm8.dynamics.com/main.aspx?appid=68968382-8ff4-ea11-a815-000d3a3dfcae&forceUCI=1&pagetype=entitylist&etn=account&viewid=00000000-0000-0000-00aa-000010001001&viewType=1039&flags=FCB.CommandChecker=true&ribbondebug=true

It can be a form

https://yourOrg.crm8.dynamics.com/main.aspx?appid=68968382-8ff4-ea11-a815-000d3a3dfcae&forceUCI=1&pagetype=entityrecord&etn=account&id=aaa19cdd-88df-e311-b8e5-6c3be5a8b200&flags=FCB.CommandChecker=true&ribbondebug=true

It can be Sub Grid 

The post Migration to UCI : Ribbon button not visible / Hidden , Debug Entity Ribbon application command bar using command checker appeared first on Microsoft Dynamics 365 Blog.

]]>
https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/09/debug-ribbon-button-mscrm.png?fit=2550%2C1384

While the transition to new UCI, We might have seen a few ribbons (OOB or custom) would not be visible in UCI and we checked every enable disable rule nothing looks wrong, and in legacy, its working fine, In this post we will check how we can debug each button i.e which display , enable rule or action failing on a button

There is a new command available in UCI to help us troubleshoot the ribbon, It will show Button Properties, Command Properties like Action, Enable Rule, Display rule, and the best part is we don’t have to install any tool or enable anything.

We just need to add these parameters in the entity “&flags=FCB.CommandChecker=true&ribbondebug=true”

  • It can be an entity

    https://dvmske.crm8.dynamics.com/main.aspx?appid=68968382-8ff4-ea11-a815-000d3a3dfcae&forceUCI=1&pagetype=entitylist&etn=account&viewid=00000000-0000-0000-00aa-000010001001&viewType=1039&flags=FCB.CommandChecker=true&ribbondebug=true
    
    

  • It can be a form

    https://yourOrg.crm8.dynamics.com/main.aspx?appid=68968382-8ff4-ea11-a815-000d3a3dfcae&forceUCI=1&pagetype=entityrecord&etn=account&id=aaa19cdd-88df-e311-b8e5-6c3be5a8b200&flags=FCB.CommandChecker=true&ribbondebug=true
    
    

  • It can be Sub Grid

 

When we click on Command Checker

  • It Gives us all Buttons available in Command Bar with property Hidden with name

  • Clicking on Button, it will elaborate more on Button Property and  Command Property, Example in below we are checking why Activate button is hidden, and in Command Properties, we can see display rule resulted in false and we can check which condition failed

This is much helpful in this time where most of us are transitioning from legacy to UCI and get many buttons which are hard to identify why they are not visible in UCI but same in visible in legacy WebClient. Thanks

The post Migration to UCI : Ribbon button not visible / Hidden , Debug Entity Ribbon application command bar using command checker appeared first on Microsoft Dynamics 365 Blog.

]]>
4167
Error : getFormContext is not a function in UCI , Ribbon Button http://microsoftdynamics.in/2020/08/22/error-getformcontext-is-not-a-function-in-uci-ribbon-button/ Sat, 22 Aug 2020 13:26:24 +0000 http://microsoftdynamics.in/?p=4089 The post Error : getFormContext is not a function in UCI , Ribbon Button appeared first on Microsoft Dynamics 365 Blog.

]]>

When passing primaryControl in Ribbon WorkBench we use it as executionContext and then get FormContext out of it.

But when same thing is done on UCI we get the Error getFormContext is not a function

We got this error in UCI and not in Legacy WebClient,

  1. We were Passing CRM Parameter PrimaryControl to Button in Ribbon workbench

  2. In JS we were getting FormContext from primaryControl(Executioncontext) which was working fine in the Legacy app

    function readXML(primaryControl) {   
    var formContext  = null;
     if (primaryControl!== null) { 
                formContext = primaryControl.getFormContext(); 
             }
        }
    }
  3. But when same is called in UCI we get ” ” Script Error, Because here we need to treat primary control as formContext

So final change needed in Code is as below

function readXML(primaryControl) {   
var formContext  = null;
 if (primaryControl!== null) {
         if (typeof primaryControl.getAttribute === 'function') {
             formContext = primaryControl; //called from the ribbon.
         } else if (typeof primaryControl.getFormContext === 'function' 
                 && typeof(primaryControl.getFormContext()).getAttribute === 'function') {
            formContext = primaryControl.getFormContext(); // most likely called from the form via a handler
         }
    }
}

The post Error : getFormContext is not a function in UCI , Ribbon Button appeared first on Microsoft Dynamics 365 Blog.

]]>
4089
OOB Rich Text Html editor control now available only for Unified client control http://microsoftdynamics.in/2020/08/16/oob-rich-text-html-editor-control-now-available-only-for-unified-client-control/ Sun, 16 Aug 2020 16:07:58 +0000 http://microsoftdynamics.in/?p=4055 Now we have out of the box Rich text Editor control available with early access to 2020 release wave 2. Please go through more post on Release 2020 wave 2

The post OOB Rich Text Html editor control now available only for Unified client control appeared first on Microsoft Dynamics 365 Blog.

]]>
https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/08/img_5f39585b6bc37.png?fit=2006%2C862

Now we have out of the box Rich text HTML Editor control available with early access to 2020 release wave 2. Please go through more post on Release 2020 wave 2 from Nishant's Blog link below

As in out last post, we added an HTML and js Web resource to enable Rich text editor control to a field without importing any 3rd party Solution, please refer the link below if still wants it in the legacy app.

Click Here: http://microsoftdynamics.in/2020/07/16/rich-text-editor-html-designer-for-microsoft-dynamics-365-crm-using-javascript-no-pcf/

Now the good news is we don’t have to write or use 3rd party PCF control or solution to enable Rich-text HTML editor Control, this is enabled when enabling Early access to 2020 release wave 2. and there are many other post can be checked from Nishant’s sir post where he explained

  1. How to enable early access to 2020 release Wave 2: Click Here
  2. Check other Posts on release 2020 wave 2: Click Here
  1. Select the multiple-line text field, below we selected description field of Knowledge article
  2. Go to Controls and click add control, Select Rich Text editor control and ADD

  3. Select where to enable here you can see all devices are compatible and that’s due to the responsiveness of UI

  4.  Save and publish and field will be enabled with Rich-text HTML control.
    Note: only for UCI forms

References :

Posts on 2020 Release wave 2 – Dynamics 365

https://docs.microsoft.com/en-us/dynamics365-release-plan/2020wave2/

The post OOB Rich Text Html editor control now available only for Unified client control appeared first on Microsoft Dynamics 365 Blog.

]]>
4055
Trial (standard) vs Trial (subscription-based) for tenant admin – Create Trail (subscription-based) Customer Engagement http://microsoftdynamics.in/2020/07/25/trial-standard-vs-trial-subscription-based-for-tenant-admin-create-trail-subscription-based-customer-engagement/ Sat, 25 Jul 2020 10:54:21 +0000 http://microsoftdynamics.in/?p=3980 When we create a new Tenant ID, there will be a new environment type option enabled for Tenant Admin "Trail(subscription Base")

Referring to Microsoft Blog: https://docs.microsoft.com/en-us/power-platform/admin/trial-environments

We get to know the difference 

Trial (standard): This is the trial type that organizations usually rollout to allow users and department managers to try new features and quickly build low-code and no-code applications and processes. Organization (tenant) admins can enable all users to create trials or only organization admins. If allowed for users, then any user from that organization, with a suitable license, can create a 30-day trial environment. After 30 days, the environment is disabled and deleted.
Trial (subscription-based): This is the trial type that organizations can use to develop larger, multi-user and multi-department solutions and do proof of concept reviews. Tenant admins can add a trial (subscription-based) to their tenant or new customers can sign up for a new tenant and become the Global admin. For new customers, an admin-managed subscription is created with a set number of licenses (usually 25 licenses); admins control license assignment to other users. An admin-managed subscription has a start and end date that can be extended.

The post Trial (standard) vs Trial (subscription-based) for tenant admin – Create Trail (subscription-based) Customer Engagement appeared first on Microsoft Dynamics 365 Blog.

]]>

There are 2 Options coming up for our talent admin user
1. Trail (Standard)
2. Trail(Subscription Based)

https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/07/img_5f1c08f6a75dc.png?fit=1496%2C901

When we create a new Tenant ID, there will be a new environment type option enabled for Tenant Admin “Trail(subscription Base”)

Referring to Microsoft Blog: https://docs.microsoft.com/en-us/power-platform/admin/trial-environments

We get to know the difference

  • Trial (standard): This is the trial type that organizations usually rollout to allow users and department managers to try new features and quickly build low-code and no-code applications and processes. Organization (tenant) admins can enable all users to create trials or only organization admins. If allowed for users, then any user from that organization, with a suitable license, can create a 30-day trial environment. After 30 days, the environment is disabled and deleted.
  • Trial (subscription-based): This is the trial type that organizations can use to develop larger, multi-user and multi-department solutions and do proof of concept reviews. Tenant admins can add a trial (subscription-based) to their tenant or new customers can sign up for a new tenant and become the Global admin. For new customers, an admin-managed subscription is created with a set number of licenses (usually 25 licenses); admins control license assignment to other users. An admin-managed subscription has a start and end date that can be extended.

Check 1: Create free Trail (Subscription Based)

  • Navigate to https://admin.powerplatform.microsoft.com/environments
  • Create a new Environment and Select Trail (subscription Based) as type
  • Create Database will be default checked

  • Select Dynamics apps

  • once done, you will find, customer engagement plain subscription in the admin. Microsoft.com

The post Trial (standard) vs Trial (subscription-based) for tenant admin – Create Trail (subscription-based) Customer Engagement appeared first on Microsoft Dynamics 365 Blog.

]]>
3980
Migration from Legacy WebClient to UCI – Ask for FastTrack and Upgrade Examiner – Not confident on transition ask Microsoft http://microsoftdynamics.in/2020/07/16/migration-from-legacy-webclient-to-uci-ask-for-fasttrack-and-upgrade-examiner-not-confident-on-transition-ask-microsoft/ Thu, 16 Jul 2020 13:27:29 +0000 http://microsoftdynamics.in/?p=3967 Microsoft has FastTrack Service and Upgrade Examiner Solution for Customer, not confidence on the Transition or wants to be 100 sure they are not missing anything

We were preparing for the transition like doing validation of web resource forms etc but to be more confident we included Microsoft support and requested for Fast Track services.

What is Fast Track ?
FastTrack helps customers deploy Microsoft cloud solutions. Customers with eligible subscriptions to Microsoft 365, Azure, or Dynamics 365 can use FastTrack at no additional cost for the life of their subscription.

and the coolest part is when we open any of the javascript it gives us the control to compare OLD CODE and NEW CODE (Suggested)

The post Migration from Legacy WebClient to UCI – Ask for FastTrack and Upgrade Examiner – Not confident on transition ask Microsoft appeared first on Microsoft Dynamics 365 Blog.

]]>
https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/07/Migration-from-Legacy-WebClient-to-UCI-Ask-for-FastTrack-and-Upgrade-Examiner-Not-confident-on-transition-ask-Microsoft.jpg?fit=1581%2C1063

Microsoft has FastTrack Service and Upgrade Examiner Solution for Customer, not confidence on the Transition or wants to be 100 sure they are not missing anything

We were preparing for the transition like doing validation of web resource forms etc but to be more confident we included Microsoft support and requested for Fast Track services.

What is Fast Track ?

FastTrack helps customers deploy Microsoft cloud solutions. Customers with eligible subscriptions to Microsoft 365, Azure, or Dynamics 365 can use FastTrack at no additional cost for the life of their subscription.

With Fast Track Service and Support, Microsoft Imported Upgrade Examiner , we will see the benefits of the same below

Benifit of Upgrade Examiner

Although in our previous post we are doing Validation Entity wise considering all component to be tested, But this solution is also helpful

  • It performs Validation on the list of component and provides suggestion and example what component needs attention

  • If we Go through Entity Data and clicks Libraries, it gives us a list of Web resource with no of Remediation found

  • and the coolest part is when we open any of the javascript it gives us the control to compare OLD CODE and NEW CODE (Suggested)

  • In some cases, we can directly copy and past New code to the library but suggested to verify 1st.

The post Migration from Legacy WebClient to UCI – Ask for FastTrack and Upgrade Examiner – Not confident on transition ask Microsoft appeared first on Microsoft Dynamics 365 Blog.

]]>
3967
Migration from Legacy WebClient to UCI – Ribbon Button Icon issue – Old Legacy WebClient Button not supported in UCI – ModernImage -SVG http://microsoftdynamics.in/2020/07/11/migration-from-legacy-webclient-to-uci-ribbon-button-icon-issue-old-legacy-webclient-button-not-supported-in-uci-modernimage-svg/ Sat, 11 Jul 2020 14:05:56 +0000 http://microsoftdynamics.in/?p=3942 Migration from Legacy Webclient to UCI - Unified client interface - Step by Step move from Legacy WebClient to Unified Client Interface UCI -

Identify the most critical components and the commonly shared component (which almost no effect)
Setup Development environment for UCI upgrade and keeping in mind we also have to support fixes and CR to legacy WebClient
So now we have 3 Properties control

Image 16 for 16*16 png or jpg image and used in classic Legacy WebClient
Image 32 for 32*32 png or jpg image and used in Classic Legacy WebClient
ModernImage SVG format independent of Resolution used in New UCI 

The post Migration from Legacy WebClient to UCI – Ribbon Button Icon issue – Old Legacy WebClient Button not supported in UCI – ModernImage -SVG appeared first on Microsoft Dynamics 365 Blog.

]]>
https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/07/Ribbon-Button-Icon-issue-Old-Legacy-WebClient-Button-not-supported-in-UCI-ModernMode.jpg?fit=1729%2C574

For New UCI Image16 and Image 32, Property Control doesn't work (PNG or JPG) and Support SVG image in New Property "ModernImage"

SVG – Scalable Vector Graphics is most suitable for the Responsive page as it can be scaled high and keeping almost same Quality and that is the Reason these images suit the New UCI Responsive page. 

Below are some advantage for Using SVG

  • SVG images can be created and edited with any text editor
  • SVG images can be searched, indexed, scripted, and compressed
  • SVG images are scalable
  • SVG images can be printed with high quality at any resolution
  • SVG images are zoomable
  • SVG graphics do NOT lose any quality if they are zoomed or resized
  • SVG is an open standard
  • SVG files are pure XML

What are the changes we need to do

  1. No change required for OOB system buttons when Transition happens it automatic updates
  2. For Custom Button and Icon we need to Add SVG image in MorderImage Property from Ribbon workBench and we can keep Image 16 and image 32 if you want but it recommended we change them too.

Check 1 For Custom Button Icon we need to Add SVG image in MorderImage Property from Ribbon workBench and we can keep Image 16 and image 32 if you want but it recommended we change them too.

So now we have 3 Properties control

  1. Image 16 for 16*16 png or jpg image and used in classic Legacy WebClient
  2. Image 32 for 32*32 png or jpg image and used in Classic Legacy WebClient
  3. ModernImage SVG format independent of Resolution used in New UCI

Below are the steps to add SVG image in Modern Image

  1. Create a New Web Resource with type as Vector Format (SVG) and Upload image

  2. Now Open Ribbon WorkBench, If not installed install it from here
  3. If button properties are disabled. right-click a select Customise button

  4. Publish the Ribbon and we can now see the correct image in our Button at UCI.

The post Migration from Legacy WebClient to UCI – Ribbon Button Icon issue – Old Legacy WebClient Button not supported in UCI – ModernImage -SVG appeared first on Microsoft Dynamics 365 Blog.

]]>
3942
Migration from Legacy WebClient to UCI – RibbonActions.js Deprecated in Dynamics 365 Unified Interface – Replace it with Execute PowerAutomate from Ribbon button using JS http://microsoftdynamics.in/2020/07/11/migration-from-legacy-webclient-to-uci-ribbonactions-js-deprecated-in-dynamics-365-unified-interface-replace-it-with-execute-powerautomate-from-ribbon-button-using-js/ Fri, 10 Jul 2020 20:05:57 +0000 http://microsoftdynamics.in/?p=3916 If your button not working most probably you are using RibbonAction or Ribbon Workflow , you might have used Ribbon Workbench to enable Command where using RibbonAction.js onto your ribbon button.
so bad news is it has been Deprecated, below is the link from ribbon workbench Blog , you can go through it to remove it from Button

https://ribbonworkbench.uservoice.com/knowledgebase/articles/132235-create-a-workflow-short-cut-ribbon-button-no-code

The post Migration from Legacy WebClient to UCI – RibbonActions.js Deprecated in Dynamics 365 Unified Interface – Replace it with Execute PowerAutomate from Ribbon button using JS appeared first on Microsoft Dynamics 365 Blog.

]]>
https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/07/RibbonActions-js-Deprecated-in-Dynamics-365-Unified-Interface-dvmske.jpg?fit=1582%2C698

We might be getting above Error with the Custom Ribbon Button where we using RibbonAction.js

-Ribbon Button not working (RibbonAction.js has been deprecated)

  • If your button not working most probably you are using RibbonAction or Ribbon Workflow , you might have used Ribbon Workbench to enable Command where using RibbonAction.js onto your ribbon button.
  • so bad news is it has been Deprecated, below is the link from ribbon workbench Blog , you can go through it to remove it from Button

https://ribbonworkbench.uservoice.com/knowledgebase/articles/132235-create-a-workflow-short-cut-ribbon-button-no-code

  • We can use JS to execute the Workflow or Action
  • or I would recommend following this post:

The post Migration from Legacy WebClient to UCI – RibbonActions.js Deprecated in Dynamics 365 Unified Interface – Replace it with Execute PowerAutomate from Ribbon button using JS appeared first on Microsoft Dynamics 365 Blog.

]]>
3916
Migration from Legacy Webclient to UCI – Responsive Design need Testing – Form Layout Issue – Composite Field issue http://microsoftdynamics.in/2020/07/08/migration-from-legacy-webclient-to-uci-responsive-design-need-testing-form-layout-issue-composite-field-issue/ Wed, 08 Jul 2020 13:00:41 +0000 http://microsoftdynamics.in/?p=3859 While Initial Pre UAT and Validation of New UCI Transition, We received a lot of issues raised by System users that Layout of form is irregular and they are having a hard time coping with it,

We knew that it's because of the responsiveness of the form and that is a good thing it's just they need to understand it better and we have to test it better

Then another was Composite Field which is split into UCI which we for sure understand to make UI more responsive, it was required but convincing system user its been tricky

We fully understand why removing composite is done and frankly don't like composite field much,

so we informed system user that this is going to be permanent for now and the reason,that to make our new UCI more responsive this might be essential step like if we want to access the environment from a smaller screen, pop from the composite field would not fit in a responsive manner and it was this easy to explain to them until we ended up creating a field to populate split value into a read-only field 

The post Migration from Legacy Webclient to UCI – Responsive Design need Testing – Form Layout Issue – Composite Field issue appeared first on Microsoft Dynamics 365 Blog.

]]>

While Initial Pre UAT and Validation of New UCI Transition, We received a lot of issues raised by System users that Layout of form is irregular and they are having a hard time coping with it,

We knew that it's because of the responsiveness of the form and that is a good thing it's just they need to understand it better and we have to test it better

Then another was Composite Field which is split into UCI which we for sure understand to make UI more responsive, it was required but convincing system user its been tricky

So receiving from layout issue by system user will be common while transitioning to New UCI especially if we have lots of information on our old legacy form to make it more interactive for the system users

  • Above image, we can see if we open New UCI of our dev in Ipad both have different section view on the screen (note these are not divided into tabs, we are taking example of the section itself, if we see new UCI of above record it will show us 2 columns instead)
  • So the Unified Client interface uses responsive web design to provide an optimal viewing and interaction experience for any screen size, device, or orientation.
  • But it better to test it from development and validation perspective before handing it over for UAT and we can do the Responsive testing in our web browser itself, chrome, firefox, etc
  • GO to the page which needs to be validated -> Press F12 to enter the dev tool and once inside devtool , you can see device button on very left top corner (chrome)

  • There we can choose between different Devices or resolution to see how the page is rendered

Then we have 1 more thing which we already informed system user about "composite field", i.e address field splits up

We fully understand why removing composite is done and frankly don’t like composite field much,

so we informed system user that this is going to be permanent for now and the reason,that to make our new UCI more responsive this might be essential step like if we want to access the environment from a smaller screen, pop from the composite field would not fit in a responsive manner and it was this easy to explain to them until we ended up creating a field to populate split value into a read-only field

The post Migration from Legacy Webclient to UCI – Responsive Design need Testing – Form Layout Issue – Composite Field issue appeared first on Microsoft Dynamics 365 Blog.

]]>
3859
Migration from Legacy Webclient to UCI – Reschedule Auto Transition date for New UCI http://microsoftdynamics.in/2020/07/08/migration-from-legacy-webclient-to-uci-reschedule-auto-transition-date-for-new-uci/ Wed, 08 Jul 2020 09:44:19 +0000 http://microsoftdynamics.in/?p=3852 The post Migration from Legacy Webclient to UCI – Reschedule Auto Transition date for New UCI appeared first on Microsoft Dynamics 365 Blog.

]]>

Even We know Microsoft announced December as transition date, It is good to check if there is any early Transition Scheduled and Approved on : https://runone.powerappsportals.com

1 thing to remember there might be early transition mentioned for your environment but until it is approved nothing will happen unless we reach forced scheduled date

  • Navigating to URL: https://runone.powerappsportals.com

  • Navigating to Environment, We will see all our organization with scheduled transition date and status

  • Clicking on Friendly name and selecting Reschedule Option on top, Don’t approve early until ready

and once ready with the Validation and customization, go ahead and Approve – Check the post where we have to share our experience on step by step transition process 

The post Migration from Legacy Webclient to UCI – Reschedule Auto Transition date for New UCI appeared first on Microsoft Dynamics 365 Blog.

]]>
3852