Microsoft Dynamics AX (Archived)

delete and dodelete method , insert and doinsert method , update and doupdate method

(0) Share

Report

Posted on by @rp@n

Hi All,

What is actual difference between delete and dodelete method , insert and doinsert method , update and doupdate method.

And what is the significance of using each? Could you please give me an example.

Thanks!

Arpan Sen

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (1)

Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Google first hit...

"The doUpdate method should be used when the update method on the table is to be bypassed."

Like I said in the other post, use the documentation, it is all in there!

Was this reply helpful? Yes No
Travis Bagley 395 on at

Like (0)

Report

You should certainly read the documentation on this, but the short answer is the do methods literally just do that one function, insert, update, or delete. They do not do any of the other methods that are usually triggered when calling such a function. For example, delete will first validate the data can be deleted by running validateDelete.

Was this reply helpful? Yes No
@rp@n 30 on at

Like (0)

Report

Thanks all of you.

I just wanted to know your thought practically. Sometimes documentation is not cleared.

So, i raised question.

Thanks!

Arpan Sen

Was this reply helpful? Yes No
@rp@n 30 on at

Like (0)

Report

Thanks Vilmos,

As per your answer if i use doInsert method then it will bypassed the insert method on the table and if i use doDelete method then it will bypassed the delete method on the table. Is't right?

Regards,

Arpan Sen

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report

Yes, correct. You bypass business logic including validations and whatsoever for the normal method counterparts. However, server-side validation still happens in aosValidate* methods for your table.

Was this reply helpful? Yes No
@rp@n 30 on at

Like (0)

Report

Thanks Vilmos,

Finally one thing.

suppose one requirement is come to me for Update or Delete or Insert records in to table.

Shall i use table.update() or table.delete() or table.insert() in to table ?

OR

use directly table.doupdate() or table.dodelete() or table.doinsert() in to table.

which one you preferred to use first?

Is there any particular reason to use doupdate() or dodelete() or doinsert() in to table? OR we can use anytime those methods for update,delete and insert record in to table ?

Thanks!

Regards,

Arpan Sen

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

insert(), update() and delete() method often contain crucial business logic, therefore you mustn't skip them! You could end up with corrupted database, data not propagating to other systems and so on.

There are situations when you want to skip them, but that must always be carefully designed. It's not common.

Was this reply helpful? Yes No
@rp@n 30 on at

Like (0)

Report

Thanks Martin,

As per my understanding we should call insert(), delete() and update() method during table operations. But when we call doinsert(), doupdate() and dodelete() methods in table?

Is there any particular conditions to call those methods?

Thanks!

Regards,

Arpan Sen

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

As Martin already said you need to use do* methods only when you do want to skip all business logic written on insert() or delete().

However you need to fully understand what are you doing and why.

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (1)

Report
I can think of a few examples:

SalesTable.insert() calls SalesTableType class (which is actually a hierarchy of classes), which do some magic and then calls the actual insertion by doInsert(). It can't call insert() because that would make an infinite loop.

If you turn a normal table to a temporary one (setTmp()), you often want to skip such methods. For example, insert() puts data to some related tables, but it's not really applicable if you inserting just a temporary record.

Sometimes you need to fix some problem in data and after evaluating logic in update() (insert(), dlete())method, you decide that you don't want to run it in this particular case. For example, you don't want to notify external systems about the change, because it's not related to them.

Was this reply helpful? Yes No