On TableExtensions we can use the OnAfterInsert OnAfterModify OnAfterDelete Triggers, that are executed after the transaction.
Sometimes it would be very usefull to specifiy these triggers on the table object directly, too.
Right now we only can use the OnAfterInsertEvent via EventSubscriptions.
Comments
yes, this would be helpful, and increase the performance. (the event subscriber will be active even if you check runtrigger = true, the onafterinsert trigger on the table / tableextension should only run like the insert - triggers. (Runtrigger true)you can create a tableextension for your own table, but for code maintenance the trigger directly in the table would help
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team