Making Custom Buttons in Dynamics 365 F&O

This guide outlines how to create a custom button for the Configurator within Dynamics 365 Finance & Operations (F&O). The button is added through a form extension and can be secured using F&O’s role-based security framework.

Prerequisites

Before proceeding, ensure the following:

• You have development experience with Visual Studio and F&O.

• You have access to a development environment.

• You are familiar with form extensions and security roles in F&O.

Procedure

1. Create an Action Menu Item:

   1. In the Application Object Tree (AOT), create a new Action Menu Item.

   2. Assign it a meaningful name (e.g., CustomConfigureXYZ).

   3. Set the following properties:

      • Object Type: Class

      • Object: XplOneClick

        

2. Extend the Target Form:

   1. Create an extension of the form that must include the button.

   2. In the form design, refer to Form Extension Example (Green square in the image below):

      • Locate the Action Pane or another suitable section.

      • Add an Action Pane Tab and Button Group (if needed).

      • Add a Menu Item Button to the Button Group.

   3. In the form design, refer to Form Extension Example (Yellow squares in the image below):

      • Set the Design property to Custom.

      • Add a component of type XplOneClickButtonControl.

      • Rename the component to XplOneClickButtonControl.

        

   4. Set the following button properties:

      • Name: CustomConfigure (or something appropriate)

      • Menu Item Type: Action

      • Menu Item Name: CustomConfigureXYZ

      • Data Source: The root table used by the Configurator

        

When the Configurator is opened via this button, it searches for an enabled Processing Entity that uses the specified table as its root.

If the standard setup does not resolve the correct entity, manually specify the Data Entity Name as a parameter on the button. The Project quotation header is an example of such a data entity. See Configure Buttons for more information.

3. To ensure only users with the corresponding Role or Duty will see the button, configure security to control access to the new button:

   • Add your Action Menu Item (e.g., CustomConfigureXYZ) to an existing Privilege, or create a new one.

   • Add the Privilege to a Duty or Role as appropriate.

     

You’ve now created a custom button to launch the Configurator from a specific form. The button uses a menu item that can be restricted via security roles. If needed, pass the data entity name as a parameter to guide Configurator behavior.