Dynamics Community Forum Thread Details

Hello MS-03040747-0,

You're facing a common requirement: preventing specific custom field values from being carried over when revising a Quote using the standard "Revise" button in Dynamics 365. Since the "Revise" button is an out-of-the-box function, direct customization is limited. However, you can achieve this using a combination of JavaScript and/or a Plugin.

Here's how you can approach this:

1. JavaScript Web Resource (Client-Side, Recommended for Simplicity):

Concept:
- Use JavaScript to clear the custom field values on the newly revised Quote form when it loads.
- This is a client-side solution, meaning it runs in the user's browser.

Implementation:
1. Create a JavaScript Web Resource:
  - Go to Settings > Customizations > Customize the System.
  - Replace "your_customfield1", "your_customfield2", etc., with the logical names of your custom fields.
  - Expand Web Resources and create a new JavaScript web resource.
  - Add JavaScript code similar to this:
  function clearCustomFieldsOnRevise(executionContext) {
  var formContext = executionContext.getFormContext();
  
  // Check if the form is a new Quote (revised Quote)
  if (formContext.ui.getFormType() === 1) { // 1 = Create form
  // Clear the custom fields
  formContext.getAttribute("your_customfield1").setValue(null);
  formContext.getAttribute("your_customfield2").setValue(null);
  // Add more custom field lines as necessary.
  }
  }
2. Add the Web Resource to the Quote Form:
  - Go to Settings > Customizations > Customize the System.
  - Expand Entities > Quote > Forms.
  - Open the Quote form you want to modify.
  - In the form editor, go to Form Properties.
  - Add your JavaScript web resource to the Form Libraries.
  - Add an OnLoad event handler and select the clearCustomFieldsOnRevise function.
  - Save and publish your changes.

Advantages:
- Relatively simple to implement.
- Client-side, so it doesn't require server-side code.

Disadvantages:
- Client-side, so it relies on the user's browser to execute the code.
- If the user has disabled JavaScript, the code won't run.

2. Plugin (Server-Side, More Robust):

Concept:
- Use a plugin to clear the custom field values on the newly created Quote record during the "Create" operation.
- This is a server-side solution, meaning it runs on the Dynamics 365 server.

Implementation:
1. Develop a Plugin:
  - Create a plugin that registers on the "Create" message of the "Quote" entity.
  - Replace "your_customfield1", "your_customfield2", etc., with the logical names of your custom fields.
  - In the plugin code, check if the Quote is being created as a revision (you can use the CreateFromQuoteId attribute to identify this).
  - If it's a revision, clear the custom field values.
  - Example (C#):
  public void Execute(IServiceProvider serviceProvider)
  {
  IPluginExecutionContext context = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));
  IOrganizationServiceFactory serviceFactory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));
  IOrganizationService service = serviceFactory.CreateOrganizationService(context.UserId);
  
  if (context.InputParameters.Contains("Target") && context.InputParameters["Target"] is Entity)
  {
  Entity quote = (Entity)context.InputParameters["Target"];
  
  if (quote.Attributes.Contains("createfromquoteid"))
  {
  // Quote is being created from a revision
  quote["your_customfield1"] = null;
  quote["your_customfield2"] = null;
  // Add more custom field lines as necessary.
  }
  }
  }
2. Register the Plugin:
  - Register the plugin using the Plugin Registration Tool.
  - Register it on the "Create" message of the "Quote" entity.
  - Register it in the Pre-Operation stage.
3. Deploy the Plugin:
  - Deploy the plugin to your Dynamics 365 environment.

Advantages:
- Server-side, so it's more reliable.
- Runs regardless of the user's browser settings.

Disadvantages:
- Requires development expertise.
- More complex to set up and maintain.

Recommendation:

JavaScript Web Resource (Option 1) is the simpler and often sufficient solution for most cases.
Plugin (Option 2) is recommended if you need a more robust and reliable solution, especially in scenarios where client-side JavaScript might not be suitable.

Remember to thoroughly test your solution after implementation.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak