DRAG DROP -
You need to resolve the performance issue with the Total Billed customer plug-in.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Scenario: User1 reports that performance is slow when viewing total billed customer time.
A plug-in for Dynamics 365 Sales automatically calculates the total billed time from all activities on a particular customer account, including sales representatives' visits, phone calls, email correspondence, and repair time compared with hours spent.
Reference:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/register-deploy-plugins
Extend the platform
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/debug-plugin 1. Register and deploy the plug-in assembly. 2. Attach the debugger 3. Run the total billed customer time query 4. Correct the failing plugin-code and compaly 5. Unregister the old version of the plug-in and reregister the new version of the plug-in
RoeIG answer is correct
This is the order I have made as well.
Agree ! Here's the link : https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/debug-plugin
Agree, that's straight up the answer from microsoft documentation.
This would make better sense because of the statement 'All testing and problem diagnostics are performed in a copy of the production environment.'
also this statement. 'Register and deploy the plug-in assembly. If there is another copy of the assembly at the same location and you cannot overwrite that copy because it is locked by Dynamics 365 Customer Engagement (on-premises), you must restart the service process that was executing the plug-in. Refer to the table below for the correct service process.'
also this statement. 'Register and deploy the plug-in assembly. If there is another copy of the assembly at the same location and you cannot overwrite that copy because it is locked by Dynamics 365 Customer Engagement (on-premises), you must restart the service process that was executing the plug-in. Refer to the table below for the correct service process.'
I think the order is right. The three first steps are to resolve the issue. That's the key: 1. Attach the debugger (to debug the current issue) 2. Run the total billed customer time query (to raise the problem and see in runtime the fail) 3. Correct the failing plugin-code (you know already what's going on. It's time to fix it. Only code up to now) 4. Register and the plug-in assembly (this new one! Once it has been solved) 5. Unregister the old version... (this is a bit redundant: you have already deployed the fixed one... but also it is now when you can unregister the other because the new one is ok). Hope it helps.
Register and deploy is not correct, the plugin was already registered. Unregister should not be needed, you can update the asambly unless you change some registration steps.
Shouldn't we put the register plugin assembly to the 1st step? Not familiar but why would we register the plugin assembly right after all the debugging? How do we debug if plugin assembly not registered? Anyone please confirm if I'm correct?
No, you shouldn't register plug in as a 1st step. You have to debug and fix incrroect lines with existing code first than after fixing them you can register compiled/corrected dll.
Should "Register and deploy the plug-in assembly." be your number one considering that you are troubleshooting the plugin as a starting point and you would not presumably know what the issue is at this point, thus making registering a plugin pointless?
Following https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/debug-plugin There is no doubt about what the first step should be. However I don't understand why we should register a plugin that is already registered. If it was not registered, it would be impossible that there's a problem with the plugin
Uncorrect! 1. Unregister the old version of the plug-in and reregister the new version of the plug-in (so I will create a new version without make confusion,and by deployment, I'll be able to remove old version) 2. Attach the debugger 3. Run the total billed customer time query 4. Correct the failing plugin-code and compaly 5. Register and deploy the plug-in assembly. -> I must load the fixing updates and go to deployment phase