Dynamics Community Forum Thread Details

AX4. Alerts. Problem with deleteing alerts and (Sys)DatabaseLog Table

--- EDIT-

Sorry this behavior was a result to a customization from a vertical solution.. The standard application does not have this problems...

Best regards..

----EDIT-

Hi all..

One strange thing I found is that when you create a new AlertRule in AX4, a record is also created in the (Sys)DatabaseLog Table.. However, when I delete the Alert Rule, the record in the DataBaseLog Table is still there. Is this a bug?? (This happens only when not using "Domains" functionality.. seems like when creating an alert rule, a record with empty Domain field is created in DataBaseLogTable, but when deleting an alert rule, if domains are not used, the record will not be deleted)

I've been for a while trying to figure out how the alert system in AX4 works. Basically I can see that when you create an alert rule, trigger it and start the batch processes, events are inserted in the EventCUD table.

Later I deleted the alerts I didn't need.. however, I could see that some insert alerts where still getting into the EventCUD and remained forever in halted status..

I started debugging why this events where inserted in EventCUD, and it was because of the system class xRecord.insert calling the Application.EventInsert method. when creating records in the affected tables.

Even if I go to SQL server and delete the records in the DataBaseLog (from AX I can't, it gives me a permissions error), the eventCUD table is still been populated.. Is there somewhere else I need to delete a reference to the deleted alert?? Has anyone found this behaviour before??

Thanks..

it´s a reproducable bug in the vm with ax2009 standard:

1. create a rule with the field condition on custtable: blocked = all

2. in the database-setup (DatabaseLog) 4 records are created (because of table AND field condition and 2 domains) (btw: is this a performance case !?!)

2.1. logTable=CustTable (77), DomainId=Admin, eventInsert

2.2. logTable=CustTable (77), DomainId=Admin, eventInsert

2.3. logTable=CustTable (77), DomainId=DP02, logField=blocked (65550), eventUpdate

2.4. logTable=CustTable (77), DomainId=DP02, logField=blocked (65550), eventUpdate

3. delete the alert rule

4. ax keeps 2 records

4.1. logTable=CustTable (77), DomainId=Admin, eventInsert

4.2. logTable=CustTable (77), DomainId=Admin, eventInsert

from that moment the user think the rule doesn´t work anymore, but it´s a fault. Ax still generates a nightmare of records in the eventCUD.

... but only if another regular warningrule still exists.

Quick Links