Skip to main content

Creating Custom Pop-Up and Email Alerts in Dynamics AX 2009

There could be occasions where an alert and/or email needs to be sent to a Dynamics AX user informing them of something that has taken place in the system that cannot be set up using the standard Dynamics AX alert such as generating an alert while running custom X++ code. To perform this function the following two snippets of code can be utilized to create pop-up alerts and/or email alerts that will be sent by Dynamics AX using the existing alert processing batch jobs.

The following example would send a pop up alert to a user notifying them that a customer record has changed:
static void create_alert( … parms if needed …)
{
EventNotificationSource source;
EventNotification event = EventNotification::construct(EventNotificationSource::Sync);
… Any Tables or variables that may be needed …
CustTable custTable = CustTable::find(’1000′);
;
event.parmRecord(custTable);
event.parmUserId(curuserid()); //this is the user that will receive the alert.
event.parmDataSourceName(‘CustTable’);
event.parmMenuFunction(new MenuFunction(‘CustTable’, MenuItemType::Display)); //this will link to the customer form
event.parmSubject(‘Customer Changed’);
event.parmMessage(‘Customer has changed, please verify’); //This message can be a single str value or you can use strfmt()
event.create();
}
The following code could be used to send an email alert to a user via the Dynamics AX alert system if ANY field in the VendTable is changed:
void generateUpdateAlert()
{
SysOutgoingEmailTable outgoingEmailTable;
SysEmailItemId nextEmailItemId;
Map map;
str SenderName, SenderEmail, To, Subject, Body;
;
SenderName = “System Administrator”;
SenderEmail = “axadmin@contoso.com”;
To = SysUserInfo::find(vendParameters::find().VendAlertUser).Email; //User ID is stored in AP parameters as to who should receive the email
Subject = “Vendor Master Record Changed”;
Body = strfmt(“Vendor %1 – %2 has been changed by %3 ”, this.AccountNum, this.Name, xUserInfo::find(false,SysUserInfo::find().Id).name);
nextEmailItemId = EventInbox::nextEventId();
outgoingEmailTable.EmailItemId = nextEmailItemId;
outgoingEmailTable.IsSystemEmail = NoYes::No;
outgoingEmailTable.Sender = SenderEmail;
outgoingEmailTable.SenderName = SenderName;
outgoingEmailTable.Recipient = To;
outgoingEmailTable.Subject = SysEmailMessage::stringExpand(Subject, map);
outgoingEmailTable.Priority = eMailPriority::Normal ;
outgoingEmailTable.WithRetries = false;
outgoingEmailTable.RetryNum = 0;
outgoingEmailTable.UserId = curUserId();
outgoingEmailTable.Status = SysEmailStatus::Unsent;
outgoingEmailTable.Message = Body;
outgoingEmailTable.LatestStatusChangeDateTime = DateTimeUtil::getSystemDateTime();
outgoingEmailTable.insert();
}
Using these two snippets of code, you can be creative as to how you go about sending alerts. These code snippets can be placed in methods of reports, forms, tables, etc. The possibilities are endless.

Popular posts from this blog

What does this mean: "The form datasource query object does not support changing its AllowCrossCompany property after the form has executed the query."?

I have made a form with datasources vendtable and vendtrans. Inside vendtable_ds.executequery() looks like this: QueryBuildDataSource queryBuildDatasource ,queryBDS_VendTrans_Invoice; ; queryBuildDatasource = this.query().dataSourceTable(tablenum(vendtable)); queryBDS_VendTrans_Invoice = this.query().dataSourceTable(tablenum(vendtrans)); if (curext() == "MASTERCOMP") { this.query().allowCrossCompany(true); } else { this.query().allowCrossCompany(false); } //FilterVendorName = stringedit control on form if (FilterVendorName.text()) { queryBuildDatasource.addRange(fieldNum(VendTable,Name)).value(strfmt("*%1*", FilterVendorName.text())); } else { queryBuildDatasource.clearRange(fieldNum(VendTable,Name)); } //FilterInvoiceNumber = stringedit control on form if (FilterInvoiceNumber.valueStr() == "") { queryBDS_VendTrans_Invoice.enabled(false); } else { queryBDS_VendTrans_Invoice.enabled(true); queryBDS_VendTrans_In...

Credit Note [Dynamics AX] using X++

This post will help to create credit note for a sales order based on the invent lot id. All the invoices raised for a particular sales line – Lot Id will be raised back as a credit note. Information on Credit Note: A credit note or credit memorandum (memo) is a commercial document issued by a seller to a buyer. The seller usually issues a Credit Memo for the same or lower amount than the invoice, and then repays the money to the buyer or sets it off against a balance due from other transactions Below Code will help to create credit note for all the invoices raised against the sales line -lot id. Please note: This code can be customized as per your requirements. This is just a template to help creating credit note using X++ code. Please test the code before use. static void SR_CreateCreditNote_Sales(Args _args) { // Coded by Sreenath Reddy CustInvoiceTrans custInvoiceTrans; Dialog dialog = new Dialog(“Create credit note – for sales.”); DialogField dfInv...