Scribd
Upload
845 views2 pages

MS Dynamic 365 Interview Question and Answers Practical Scenario Based

The document contains answers to common Microsoft Dynamics 365 scenario based interview questions. The answers discuss how to handle issues in UAT and production environments, how to export and import solutions with multiple patches between environments, and how to add patches to existing solutions in production.

Uploaded by

j.vidhya Shree
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
845 views2 pages

MS Dynamic 365 Interview Question and Answers Practical Scenario Based

The document contains answers to common Microsoft Dynamics 365 scenario based interview questions. The answers discuss how to handle issues in UAT and production environments, how to export and import solutions with multiple patches between environments, and how to add patches to existing solutions in production.

Uploaded by

j.vidhya Shree
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MS dynamic 365 Scenario Based Interview Question

1. What will we do if we are facing the issue in UAT and Production?


Answer: First, we must understand which component is causing the issue. If any solution
component causes an issue, then we need to fix the issue in Development and re-test and
move the solution patch to UAT and production. For Plugins we can use profilers for
debugging to understand root cause, plugin trace to analyze. Need to check if the issue is
coming due to data issue so that we can fix data.

2. How to export solution to production, if solution have multiple patches?


Answer: If a solution has multiple patches, you have to export the patch and import it into
the target environment. For bug fixes you can use patches. For major feature or minor
feature, you can upgrade while importing close.

3. How to apply business rules to the section?


Answer: You cannot apply Business Rules for sections, you need to write JS.

4. How to work in Jira tool?


Answer: Jira is a software application that helps teams manage projects, track issues, and
automate workflows. It was developed by the Australian software company Atlassian.

5. Can we apply automation in import and export the solution? If yes how?
Answer: We can automate solution deployment using DevOps CI, CD Pipelines with some
Power Sheel script and Power Platform Build Tools.

6. If one solution has used the same form in multiple tables with different configuration, is it
shown any error at the time of exporting to production?
Answer: If all the dependent components are in place there will be no error.

7. Can we import multiple solutions in one environment?


Answer: Yes.

8. For sales and service, we used one solution or 2 different? If one, then if both solution
contain have same entity, is there any conflict happen in production?
Answer: Better to create 2 solutions depending on module. If one solution is created, we
have to be careful about change override otherwise there is no issue.

9. In UAT and production if some issue arises then how to resolve that one?
Answer: First, we must understand which component is causing the issue. If any solution
component causes an issue, then we need to fix the issue in Development and re-test and
move the solution patch to UAT and production. For Plugins we can use profilers for
debugging to understand root cause, plugin trace to analyze. Need to check if the issue is

10. How to add patch and how it will work?


Answer: A patch is a subset of a solution used to move a smaller number of components from
source environment to target for bug fix scenarios. Instead of moving the whole solution we
can move delta changes in a small solution called a patch. Patches are bug fixed components
placed on top of master solution. Once you upgrade the solution all the components are rolled
up to master and patches are deleted.

11. How to add patch in production with existing solution?


Answer: Create a patch in development and export and import in production.

12. How to identify where the issue is a bug or a configuration issue? How to fix the bug in
production?
Answer: By debugging code and running use cases we can Analyse Root Cause. For
production server log files, traces help to do Root Cause analysis. For production bug fix see
number 1 questions answer.

13. If some error is showing in production, then How to identify that is from functional side or
technical error?
Answer: By debugging code and running use cases we can Analyse Root Cause. For
production server log files, traces help to do Root Cause analysis. For production bug fix see
number 1 questions answer.

You might also like