Fusion Recorder FAQ

How the Fusion Extension Works

Fusion Dynamics 365 extension is developed by Leapwork. The Fusion Extension captures and replays user actions by creating a unique identifier for each element you interact with on D365 F&O.

During Recording:

When user click or interact with a button, field, or other element, the extension intelligently identifies the best attributes to create a reliable identifier for that element.

This ensures the fusion extension can find the same element later, even if the page layout changes slightly.

During Replay:

The fusion extension uses the stored control name to locate the element again by working its way from the top of the page down to the exact component you interacted with and recorded.

This allows the automation to replay your actions accurately without manual adjustments.

Security considerations:

  • It does not collect or transmit any data externally.

  • It does not access or store cookies, passwords, or form data.

  • Its sole function is to enable automation within the bounds of the Leapwork platform for predefined flows and test cases.

  • It communicates locally with the Leapwork Controller to perform actions securely and in real time.


.NET 6 Runtime Dependencies for Running Fusion Recorder

Note: Not required after .NET 8 build 2025.3

Why do I need .NET 6 to run Fusion Recorder?

Fusion Recorder relies on .NET 6 features for execution runtime. Without the runtime, the recorder will fail to launch or crash during execution.

Where can I download the .NET 6 runtime?

While the Leapwork installer tries to download and install it automatically, we recommend pre-installing it to avoid failures due to firewall or proxy restrictions.
Note: .NET 6 is pre-requisite for D365 F&O recorder to work properly, without it the new Fusion recorder will not work.

Step 1: Check Installed .NET 6 Runtime Versions

Before installing, verify if the required .NET 6 runtime components are already present on the system.

Check .NET 6 Windows Desktop Runtime

  1. Open Command Prompt or PowerShell.

  2. Run the following command:

dotnet --list-runtimes
  1. Look for an entry similar to:

Microsoft.WindowsDesktop.App 6.0.36 [C:\ProgramFiles\dotnet\shared\Microsoft.WindowsDesktop.App]
  1. If Microsoft.WindowsDesktop.App 6.0.36 is present, skip installation of Windows Desktop Runtime.

If it is missing, install .NET 6 Windows Desktop Runtime:

  1. Download the installer from the official source: Windows Desktop Runtime 6.0.36 (x64)

  2. Run the downloaded .exe file.

  3. Follow the installation wizard:

    1. Accept the license agreement.

    2. Click Install.

    3. Wait for the installation to complete.

  4. Restart the machine if prompted.

Install .NET 6 Core Runtime

  1. Download the installer from the official source: ASP.NET Core Runtime 6.0.36 (x64)

  2. Run the downloaded .exe file.

  3. Follow the installation wizard:

    1. Accept the license agreement.

    2. Click Install.

    3. Wait for the installation to complete.

  4. Restart the machine if prompted.

Will it require internet access?

Yes. The installer requires internet access once to fetch .NET runtime and other dependencies. However:

  • If your company firewall blocks downloads (like EXEs or MSI), then runtime installation will fail.

  • In such environments, download the installer and .NET runtime manually on a machine with internet and copy them over to the target system.

What error appears if internet or port access is blocked?

The installer won't show any errors, as it doesn't block the complete installation process. However, if the required ports or internet access are restricted, the Fusion Recorder will not function.

What if EXE download is blocked due to company policies?

Many enterprise IT policies block automatic EXE downloads. In this case:

  • Ask IT to whitelist the required endpoints.

  • Alternatively, provide an offline installer that includes all prerequisites.

https://builds.dotnet.microsoft.com/dotnet/WindowsDesktop/6.0.36/windowsdesktop-runtime-6.0.36-win-x64.exe

https://builds.dotnet.microsoft.com/dotnet/aspnetcore/Runtime/6.0.36/aspnetcore-runtime-6.0.36-win-x64.exe

How can I quickly check if the required runtimes are installed?

  1. Open a command prompt and run

dotnet --list-runtimes. 

This will display all installed .NET runtimes. Ensure that below .NET 6 Runtime are listed.

Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]

Chrome/Edge Extension Issues for Fusion Recorder

The Chrome or Edge extension is not loading on browser launch. What could be the reasons?

There are several common causes:

  • Enterprise policies may block extension installations entirely.

  • Group policies might prevent auto-loading of extensions.

  • Antivirus or endpoint protection tools may interfere with the extension.

  • Corrupted extension state or incomplete installation.

What happens if the extension is blocked or not allowed?

The browser will launch but remain on a blank screen. No further automation or recording actions will be triggered.
To resolve this, the Leapwork/Fusion Recorder extension must be whitelisted by your IT department if it is being blocked by policy.
Step 1: Open Group Policy Editor

  1. Press Win + R, type gpedit.msc, hit Enter.

  2. Navigate to the appropriate policy path:

For Chrome:

Computer Configuration > Administrative Templates > Google > Google Chrome > Extensions

For Microsoft Edge:

Computer Configuration > Administrative Templates > Microsoft Edge > Extensions

Step 2: Configure the Whitelist

  1. Find and double-click: “Configure extension installation whitelist”

  2. Set to: Enabled

  3. Click Show.

  4. Add the extension ID:  

  5. Click OK, then Apply.

Step 3: Force Group Policy Update

  1. Open Command Prompt as Administrator

  2. Run

    gpupdate /force.
    

Step 4: Relaunch the Browser

  • Open Chrome or Edge

  • Visit chrome://extensions/ or edge://extensions/

  • Ensure the extension is no longer blocked

  • If it’s not installed yet, you can now manually install it from the Web Store or deploy it via policy

Alternative Method: Registry Editor

Use this only if Group Policy Editor is unavailable or you're managing settings manually.

Steps:

  1. Press Win + R on your keyboard.

  2. Type regedit and press Enter to open the Registry Editor.

  3. In the Registry Editor, navigate to the correct path:

    • For Chrome:
      HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallWhitelist

    • For Edge:
      HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallWhitelist

  4. If the ExtensionInstallWhitelist key does not exist:

    1. Right-click on Chrome or Edge.

    2. Select New → Key.

    3. Name it ExtensionInstallWhitelist.

  5. Inside the ExtensionInstallWhitelist key:

    1. Right-click anywhere in the right panel.

    2. Select New → String Value.

    3. Name the new value 1.

    4. Double-click it and set the value data to:

  6. Close the Registry Editor.

 Optional: Force Policy Refresh

Run

gpupdate /force

or simply restart the computer.

Why is whitelisting the extension necessary?

The Fusion Recorder relies on the browser extension to:

  • Detect and interact with web elements.

  • Communicate between the application and the browser.

  • Capture actions and DOM data during recording.

Without the extension:

  • The recorder cannot function in the browser.


Recorder Port Conflicts for SignalR

My recorder is not connecting, could it be a port issue?

Yes. The recorder uses SignalR, which operates over specific ports (e.g., 5000/5001). If another application (like IIS Express or Docker) is using these ports, it may cause a conflict.

How can I resolve port conflicts?

You can either update the default port settings in the configuration file or terminate the conflicting process using netstat, taskkill, or Task Manager.

Do I need to expose these ports to the public?

No. These ports are used internally only. The communication occurs locally between the agent and the browser extension, there's no need to expose them externally.

How can I enable the Fusion F&O Recorder to work with additional domains?

You can add extra domains to the Fusion F&O Recorder configuration file to allow recording across multiple trusted domains (for example, when your Dynamics 365 setup spans more than one domain). This is useful in cases where the recorder does not capture actions because the page belongs to a different domain.

Can I view logs for the browser extension?

Yes, open the browser’s developer tools (F12), navigate to the Console tab under the extension's background page, and observe runtime logs.

Is the old web extension compatible with the newer Fusion Recorder extension?

No. The new extension is designed to work only with the updated Fusion Recorder and is not backward-compatible with previous versions.

Can we use web blocks, such as Start Web Browser, with the new Fusion Recorder?

No. The Start Web Browser and similar web blocks are not compatible with the Fusion Recorder blocks. Fusion Recorder uses a separate mechanism to launch and control the browser.

Will this work with Leapwork Cloud?

Yes.