---
title: "Alert Links - Lasernet Finance and Operations Connector User Guide"
slug: "alert-links"
description: "Lasernet Query reports can be automatically triggered using Alert links. Alert links link Alerts in standard Finance and Operations to Lasernet Query reports."
updated: 2025-10-27T10:31:47Z
published: 2025-10-27T10:31:47Z
canonical: "kb.lasernetgroup.com/alert-links"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Alert Links

## Use Alerts to Trigger a Report Run

Lasernet query reports can be automatically triggered using Alert Links. Alert Links link alerts in standard Dynamics 365 Finance and Operations to Lasernet query reports.

This is useful in situations where no report exists for a process/flow, when a report needs to be triggered upon record deletion or insertion, or when a value for “Field is changing” (such as when an order status changes).

Other examples are:

- Triggering a report once a credit max/limit changes.
- Requiring an additional report run, such as a label, when an order status changes.

Note

Alert Links work only with custom queries and not with replacement reports, because replacement reports have a point of execution, as the process that starts these reports is the posting and journal.

A custom alert can be created on any form (Purchase orders, Sales orders, etc) by navigating to the Action pane > **Options** tab > **Share** group > **Create a custom alert**.

In the following example, we will create an alert from the **Purchase orders** list page. To do so, navigate to **Accounts payable** > **Purchase orders** > **All purchase orders**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-3SH6Y7BE.png)

## **Create Custom Alert**

To create a custom alert, follow these steps:

1. Click **Create a custom alert**. A window will open.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-LDCPK3N8.png)

1. You can either use **All fields** or select a specific field.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-RKHGS94S.png)

Selecting **All fields** enables the user to select **Event Record has been created** or **Record has been deleted**. **Event Record has been created** prepares an alert once a record is inserted, while **Record has been deleted** prepares an alert once a record is deleted within the selected table.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-IEVL9DNX.png)

Selecting a specific field would provide some additional events.

Example

Selecting a field such as **Customer reference**, for example, provides the following option for an **Event**:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-ZJTO4LAM.png)

## Link the Alert to a Report in Lasernet FO Connector

Linking an alert to a report in Lasernet FO Connector can be achieved in two ways.

- First method:

1. Open **Manage my alerts** from any Dynamics 365 Finance and Operations form by navigating to the Action pane > **Options** tab > **Share** group > **Create a custom alert**. This is a standard form that will show all your alerts.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-XAGHAVIK.png)

1. Link to the report in Lasernet FO Connector. In the **Alert with reports** FastTab, add a record to the report in Lasernet FO Connector.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-6G5KMXO8.png)

- Second method:

Navigate to **Lasernet** > **Common** > **Reports** > **Setup** > **Alert links**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-OWWTG2FF.png)

## Set Up the Link to the Alerts in Lasernet FO Connector

The **Alert links** form can be accessed both from **Lasernet** > **Common** > **Reports** > **Setup** > **Alert link**, and from **Accounts receivable** > **Customers** > **All customers** > **Options** > **Manage my alerts** > **Setup**.

To set up the link to the alerts, follow these steps:

1. Select the **Rule Id** that was created through the **Create a custom alert** option, and toggle the **Active** button to **Yes**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-V4IZRYRC.png)

1. Select the required **Destination**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-L69SZT6K.png)

Alerts are a backend process, and **Lasernet Screen** is therefore not a valid destination.

The following warning is displayed when the **Lasernet Screen** is used as a destination for the alert:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-UX7H6TMR.png)

Warning

Unable to execute Lasernet report VendPurch_BalanceCheck on event 000302, as screen or standard destinations are not allowed in event links

1. Select **Default ranges** in the **Records to Include** FastTab. The default ranges define which records to include when the report is automatically run. They work in a similar way to the **Form links** in Lasernet FO Connector.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-LCJJFC0G.png)

1. In the **Default query ranges** dialog, either locate or add the fields that will be used as a **Range**. Provide a **Range** for the specified field. Selecting a value from the dropdown hardcodes the range to a specific value, while clicking the **Expression editor** button provides the option to dynamically set the **Range** value.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-LE37I975.png)

## Context in Lasernet FO Connector when Working with an Alert

Alert Links can use the value **Context** within **Default ranges**. **Context** provides information about the alert and also contains details about the record that triggered it. This is useful because using **Context** will dynamically identify the record for which the alert was triggered, and the query will automatically run based on this value.

1. Open the **Default ranges** for an Alert Link and click the **Expression** button on the desired field to open the Expression Editor. (Review the last step from the previous section).

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-LQ994MO3.png)

1. Open the dropdown on the **Select Value** field and select **Context**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-QBCPCLVC.png)

1. Open the dropdown again to see the **EventLink** list. Select the **EventLink** associated with your **Rule ID**.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-KSY677WK.png)

1. Selecting the **Rule ID** provides information about the alert and the table triggering the alert – the table **PurchTable** is shown in the following image:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-G2ARMWLY.png)

1. Open the dropdown again to see the list of fields for the selected table. Select the field associated with your range. The following example illustrates a report range in which the field **PurchID** is used from the record that triggered the alert:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-TTCMT2PY.png)

1. Click **OK** to close the Expression Editor. The **PurchID** from the **Context** will be used, so that only records with the same **PurchID** as the record triggering the alert will be fetched.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-OTMPYDWN.png)

Note

It is possible to specify default query ranges for a report with multiple criteria.

For example, if an alert needs to be associated with a specific purchase order (which is associated with a vendor account), it can be specified as follows:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-Z13J94QX.png)

This approach is recommended over creating two Alert Link rules with conditions, as only one condition is possible by design per alert rule in Dynamics 365.

### Context - EventType

Context provides information about the alert and also contains details about the record that triggered it. The previous steps guided us on how to use context to retrieve information regarding the table and field that trigger the alert. Alternatively, context can also retrieve information using EventType.

The EventType enables the retrieval of information about the Current and Original Value.

This is useful when triggering an alert through a specific field, such as **Credit max**, **Status**, **Delivery date**, or any other field.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-OTEB9DO7.png)

Use the Context.EventLink_xxxx.EventType.**parmCurrentValue()** and **parmOriginalValue()** to retrieve the **Current** or **Original** from a previously changed field.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-OM7386SG.png)

## **Required Batch Jobs for Alerts**

Ensure the following batch tasks are running as they are used for the alerts in standard Dynamics 365 Finance and Operations:

**Change-based alerts**:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-OGVD1Z37.png)

**Due date alerts**:

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-U67MBGI8.png)

If any batch job has not started, it can be initiated from **System administration** > **Periodic tasks** > **Alerts**. A **Recurrence**, such as every two minutes, must be set so that alerts are processed regularly.

![](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/image-H0YXRXXC.png)

Batch jobs are a standard Dynamics functionality that processes and generates alerts on a regular basis, as specified by the recurrence. The Lasernet query is generated when the batch job runs, and the alert is generated. If archiving is enabled, the generated Lasernet query can be seen in the Lasernet Archive.