There are must select following entities while migrating configuration data of product catalog from one instance to another instance (Dev to Preprod /Preprod to Production) using Configuration Migration Tool.
formContext = executionContext.getFormContext();
var caseType = formContext.getAttribute(logicalname).getValue();
changeForm(“Case for Interactive experience”);
var currentForm = formContext.ui.formSelector.getCurrentItem();
var availableForms = formContext.ui.formSelector.items.get();
if (currentForm.getLabel().toLowerCase() != formName.toLowerCase())
for (var i in availableForms)
var form = availableForms[i];
// to find a form based on the name
if (form.getLabel().toLowerCase() == formName.toLowerCase())
Call this function on page load event and make sure that this code is present on all other forms.
Testing: I am creating case record from default case form by putting up case type as Trial order.Once record is saved.It will navigate screen to trial order case form and have similar behavior for claims case form too.
Hope it is informative! 🙂 Keep dynamics-power with you.
While I was working on Ribbon Workbench customization, one
of my colleague addressed me that custom button icon is showing as jigsaw image
in UCI interface whereas button’s icon is showing as desired in classic
Interface. My colleague was questioning if it is a Microsoft issue or anything
else which is missed to be done?
I went to Ribbon Workbench Customization, There I noticed
one more new input i.e. ModernImage.
Modern Image supports Vector format (SVG) and responsible for UCI(Unified
Client Interface) visibility.
Therefore,16X16 image, 32X32 image is responsible for Classic
View. Even you can test it at your own. Remove these 16 or 32 png from Ribbon Work
Bench then publish it, you will not see them in Classic Interface😊
All you need to do it. Create a Vector format (SVG) web
resource. Go to Ribbon Workbench, Select your Solution, Browser your SVG icon
image under Modern Image and then good to go to publish it.
Even though Dynamics 365 Customer Engagement is being changed a lot. Perhaps, some technical questions are pretty basic and commonly asked in most of the interview. I have listed few of them below:
Question #1: How will you optimized form performance when you have multiple tabs/grids on the entity form.
Answer: While placing sub-grid on form we should unchecked the Expand this tab by default from tab properties. It saves page rendering time and enhance the page load performance.
Question #2: What is the difference between Plugin and Workflow? (Being a developer we always deals with plugin and workflow. So, This is something from which you can’t remain untouched. 😊)
Answer: Some of the differences are detailed below:
Business Users /Functional Consultant
Nested Child Process
Organization User Business Unit Parent:Child Business Units
Organization User Context User Impersonation (To run plugin on another user context.)
Get External Data
Record is created Record Status changes Record is assigned Record fields change Record is deleted
Create Update(Filtering attribute) Delete Associate Disassociate Status Change Assign to Owner
Executed After Save
Can run on Relationship
N:1(lookup on the record)
Note Compatibility* : Earlier Workflow was asynchronous until Microsoft enable Convert to a real-time Workflow.
Note Nested Child Process*: Nested Child Process is very useful. Commonly used scenario i.e.to send mail to employee on their birthday.
Note Can run on Relationship*: Workflow cannot automatically update all the contact addresses when the parent account address changes. But this can be done with a plug-in.
Question #3 : What will execute first business rule or java script?
Answers: execution order is defined below:
1.System Java Script(Source code by MS)
2. Custom Java script
Reason: business logic is applied to Business rule will be converted to Java script and then gets executed On other side custom java script doesn’t required any conversion So it saves conversion time and executes first.
Question #4: What are the event pipeline stages and its number?
Answer: Event pipeline stages are 4 and plugin/workflow can register in 3 stages out of 4.
It is executed before the main system operation. Registered plugin gets executed before the database transaction. Pre-validation stage occurs prior to security role check and mainly used delete plugin message.
It is executed before the main system operation. Registered plugin gets Executed within the database transaction.
Platform Core Operation
It doesn’t allow to register custom plugin. it is the main operation of System(Source code by Microsoft)
It is executed after the main system operation. It allows to register custom plugin. Registered plugin gets executed within the data base transaction.
Question#5: What is the time limit of plugin/Custom workflow execution?
Answer: It’s 2 minutes(like Maggie 😊)Irrespective of Synchronous/Asynchronous,There is 2 minutes time limit imposed on execution. If execution exceeds the limit a System.TimeoutException is thrown.
Note: While we code and gets Business Error“This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again” which is showed 7 iteration steps. Reason being, execution time limit is 2 minutes.
Earlier I wasn’t known how to integrate HubSpot to Dynamics 365 then I started deep diving into it and come to know there are various methods to do it. These methods are mentioned as below:
HubSpot integration to Dynamics 365 using Zapier
Dynamics 365 CE integration to HubSpot using Logic Apps (If you want to see ‘how’ click here)
Here I will tell you the detailed steps to integrate HubSpot
to Dynamics 365 Customer Engagement using Zapier. Zapier is a web automation
app and allows HubSpot to connect with several other 1000’s application and
technology. With Zapier I will build Zaps which will automate the process.
#2: Enter Email Address and Password then click on Log in.
#3: On the top, Click to settings,
#4: In left panel, Expand
Integrations and click on Apps below API Key.
#5: Click on Connect an app
#6: You will see some recommended apps over here. Though our
intended application is Zapier. Click on Zapier you will be navigated to next
#7: Click on Connect. Since it’s not Microsoft Technology. It doesn’t support single sign-on until you sign up with the same account. So, in next screen it will ask you login to Zapier. Here, I am assuming that you have Zapier credentials with you already. If you don’t have. Do sign up and be continued as per below detailed steps.
Now you are connected to Zapier.
Section 2: Making of Zap once you are connected with zapier.
#1: Now you are at Zapier screen where you will create Zap.
Click on Make a Zap!
#2: Write name of your zap. I wrote MydemoZap. then choose a
Trigger App. I searched for HubSpot and get connected with it.
#3: Choose Trigger. I have chosen New Contact. It triggers when contact is created. Move further, click on Save+Continue.
#4: Connect to your HubSpot instance. One screen will pop-up, on click of Connect an Account. it will ask for permission. Click on Grant Access to give permission of HubSpot then this screen will disappeared and you will be on same page, Post that click Save+Continue.
In this step, I am collaborating consecutive screen as
Thus you are done with trigger now. 🙂
#5: Add a new step for Action. Search for Dynamics 365 CRM Action. I have chosen create contact since it is our objective. (Refer objective).Moving forward click on Save+Continue.
#6: Connect to Dynamics 365 CE. Click on Connect An Account.
Post that, paste organization url in new pop up screen and click on to Yes,
Continue. To authenticate yourself put user credentials and make sure that you
are using administrator user. You will be land on same page. Click on
I have collaborated screen for this step as below:
#7: Edit Template is 2nd last step. As per your requirements map the values in given template. I have mapped for first name, last name and email address. 😊 for demo and click on Continue.
#8: Full and final step is here. 🙂 Click on Finish and Enable your zap at the top on the same page.
We are ready with our integration. Yipee!
I went to HubSpot and created new contact as per below screen:
And same contact is created in Dynamics 365 Customer Engagement.
Limitation: Generally, Business doesn’t permit to use Zapier since Zapier stands with several pricing plans. However, it costs way more to business.
Other than this, the Clock is still ticking for versa data flow from Dynamics 365 CE to HubSpot.
I was assigned a task where business requirements were to integrate HubSpot to Dynamics 365. Being a Dynamics’ folk, I was unknown to the term HubSpot itself and was also like other Dynamics’ enthusiasts who were also new to this term. Then during my research journey, I got to know that it is CRM like our Dynamics 365 CRM or like any other CRM which is present in the market. HubSpot has its two flavors Professional and Enterprise. Marketing Hub Professional and Sales Hub Professional is more advance than Sales Hub Enterprise and Marketing Hub Enterprise.
Since it was POC I don’t have HubSpot instance yet. This was
the time when I realized that I should have source(HubSpot) instance first to
integrate it with Dynamics 365. It should be my priority to get HubSpot
instance ready before starting the actual work.
Here, are the steps to get your HubSpot instance ready.
Microsoft has released a preview of its April release on 1st Feb 2019 that allows us the flexibility to explore the features, adoption of all changes and the user experience updates for Dynamics 365 and the Power Platform which will be enabled by default in April 2019.
Note: Once you enable the April 2019 update, it can’t be turned-off.
Step2: On selecting, it will go to environment’s hub, where click on manage.
Step3: Click on Active now, it will take you to confirm screen.
Step4: Enter your environment name and click on continue.
It will take a while to activate the April 2019 update. Once it’s done same will be notified as “April 2019 update is now active” and April 2019 update is On now in update section on the bottom or right hand side.