Find User Who Added Code to Dynamics 365 Supply Chain Management Form | Exam MB-500 Microsoft Dynamics 365: Finance and Operations Apps Developer

Find User Who Added Code to Dynamics 365 Supply Chain Management Form

Question

You are a Dynamics 365 Supply Chain Management developer.

You are working on a project by using Visual Studio.

Several users check out a custom form version control and modify the form.

You need to find the user that has added a specific line of code to the form.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D.

In Visual Studio, Go to source control explorer > Select the object > right click > View history Reference: https://dynamicsuser.net/ax/f/developers/93354/how-to-rollback-a-change-set-completely-automatically-in-tfs.

As a Dynamics 365 Supply Chain Management developer, you may need to collaborate with other users to modify a custom form version control using Visual Studio. When multiple users are working on the same object, it can be challenging to track changes made by each user. Therefore, to find out which user has added a specific line of code to the form, you can follow the steps below:

  1. Open Visual Studio and navigate to the solution that contains the custom form version control.

  2. In Solution Explorer, locate the custom form version control that you want to investigate.

  3. Right-click on the form and select View History. This will open the Object Version Control History window.

  4. In the Object Version Control History window, you will see a list of all the changes made to the form, including who made the changes and when.

  5. To find the user who added a specific line of code to the form, you can use the search functionality in the Object Version Control History window. Enter the text of the line of code in the search box and click the search button. The search results will show you all the changes that include the text you entered, and you can identify the user who made the change by looking at the details of each change.

Option A and Option D are similar as they both involve using Visual Studio to navigate to the object in Application Explorer or Object Designer and then selecting View History to open the Object Version Control History window. Option B is not correct as it suggests navigating to the object in Solution Explorer and then selecting View History, which is not the correct option for viewing version history. Option C involves adding the object to a new solution, which is not necessary for viewing version history and may cause unnecessary complexity.