MH506 – Proactive Monitoring: Setting Up Alert Events for MHAX Subscriptions in Dynamics 365FO
Introduction
This article will detail the configuration of alert events in Dynamics 365 FO to monitor and subscribe to events in Logic Apps, ensuring the successful extraction of outbound events in near real-time.
Step-by-Step Instructions to Enable Change-Based Alerts in D365FO
Access the Business Event Catalogue
1.1 Sign in to D365FO:
- Log in to your Dynamics 365 Finance and Operations environment.
1.2 Navigate to Business Events:
- Go to System administration > Setup > Business events > Business events catalogue.
1.3 Locate the Change-Based Alerts Event:
- In the Business Events catalog, search for the BusinessEventsAlertEvent.
- You can filter by Event ID or scroll through the list to find it.
Enable the Business Event
2.1 Enable the Event:
- Click on +Activate
Configuring Endpoints is not required
- Both Azure Logic Apps and Power Platform offer out-of-the-box actions to read Alert business events. Therefore, configuring an endpoint is not required, as it will be automatically created upon the first data retrieval.
Here’s the high-level summary presented in a table format:
| Endpoint Type | Description | Pros | Cons | Use Case | Cost |
|---|---|---|---|---|---|
| Azure Service Bus Queue | Queue-based messaging system for asynchronous communication, storing messages until processed. | – Decoupled communication – Message ordering – Dead-lettering | – Single consumer – Throughput limitation | Asynchronous processing, e.g., work orders or transactions | Charged based on the number of operations and storage. |
| Azure Service Bus Topic | Pub/sub model where messages are sent to a topic, and multiple subscribers receive copies of the same message. | – Multiple subscribers – Message filtering | – Complex configuration – Potential message duplication | Broadcasting events to multiple services, e.g., multi-department alerts | Charged based on operations, storage, and each subscription. |
| Azure Event Grid | Fully managed event routing service enabling event-driven architectures, supporting high scalability. | – High scalability – Easy integration with Azure services – Low latency | – Limited custom logic – Requires understanding of event-driven architecture | Real-time event processing, e.g., triggering workflows or functions | Pay-per-event model, with charges based on operations and event delivery. |
| Azure Event Hub | Big data streaming platform and event ingestion service, capable of processing millions of events per second. | – High throughput – Integration with big data services | – Complexity in setup and management – Higher cost | Telemetry and log data capture and analysis | Charged based on throughput units, data ingress/egress, and additional features. |
| HTTPS (Webhook) | HTTP-based callback mechanism that triggers an HTTP POST request to a specified URL when a business event occurs. | – Simplicity – Direct communication with external systems | – No retry mechanism – Scalability issues under high load | Direct integration with external systems or services, e.g., simple event notifications | Minimal cost, mainly related to running the web service or handling incoming requests. |
| Azure Blob Storage | Scalable object storage service for unstructured data, used for storing files, logs, and large datasets. | – Cost-effective – High durability and availability – Simple to use | – Not real-time – No processing logic | Data archiving and storing large datasets, e.g., business event logs or bulk data export | Charged based on data storage, read/write operations, and data retrieval. |
Set Up Change-Based Alerts batch job
3.1 Navigate to System Administration
- Go to System Administration > Setup > Alerts > Change based alerts
- Click on Options in the toolbar, and then select Create alert rule.
- Set the recurrence to 1 minute. This configuration ensures that events are sent to the Logic App every minute. These are lightweight alerts, and batch servers handle them efficiently. You may adjust the timing based on your specific business requirements.
4. Set Up Change-Based Alerts for ‘PickList-Pick’ subscription ID
4.1 Navigate to Material Handling equipment Interface Outbound queue
- Go to Material Handling Outbound Queue > Common > Outbound Queue
4.2 Filter the Outbound Queue List Page
- Filter the “Outbound Status” Column: Set the filter to display only records where the status is Ready.
- Filter the “Subscription ID” Column: Apply a filter to show records with the Subscription ID PickList-Pick.
4.3 Create a Custom Alert Rule
- Navigate to the “Alert me” Tab:
- Select the field name Outbound Status.
- Set the Event Field: Choose Is Set To and set the value to Ready.
- Configure Alert Delivery:
- Turn on the Send Externally toggle button to enable external alerts.
- Note the Rule ID: Record the Rule ID, as it will be required for triggering the Logic App.
- Save the Rule: Click OK to finalize the alert rule.
High Level configuration of Putaway events
In our use case, inbound containers are initially received at the Goods In locations and subsequently transferred to the External WMS storage locations. The External WMS then generates putaway work for these movements. Upon completion, the External WMS sends a completion message back to Dynamics to register the closure of the transaction. To facilitate this process, we will utilise the ‘Movement by Template’ work creation process.
Mobile Device Menu Item
Work Template
Location Directives
Directive action set to MHAX location
Mobile Device Menu
Movement by Template
- Process a movement on PDA
- Verify a work
- Verify Outbound Events
Tip to setup multiple alerts from same list page
When setting up alerts after the Filter List page, each alert will be unique to the records filtered. This approach is effective for our use case, where alerts need to be configured based on subscription IDs.
Please follow the steps outlined above to create alerts for the following subscriptions:
- PickList-Put
- Putaway-Pick
- Putaway-Put
Ensure to note down the alert rule ID for future reference.
Share this content:
Post Comment