How to make the regular job, an incremental job

(0) Share

Report

Posted on by Community Member

Hello Everyone !

I have write a job that copies data from one table to another. both the tables are similar. both have same number of columns with similar names and data types.

when my job runs it copies all the rows from first table to second table. But i want that every time when the job runs it only copy those rows that has been changed or added new.

Is there any default mechanism that dynamics AX provides ?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Community Member on at

Like (0)

Report

Dear Muhammad Gulfam,

If you want the job to run only on update then you can keep the following condition,

if(!TableBuffer)

{

Insert

}

else

{

Update

}

The above algorithm, first checks whether it is new record, if it is then it will insert the new row else it means that we are updating the existing row only. If you need further clarifications please let us know.

Thanks,

Was this reply helpful? Yes No
startax 1,845 on at

Like (0)

Report

Hi Gulfam,

Without any condition in your job its not possible to insert only new records in other table.

Here is the sample code that first check CSV and then insert and update data in table accordingly you have to give some condition to check existing data and match with new entry in your table.

howtoax.com/how-to-insert-and-update-data-from-csv-in-ax-2012-using-x

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I dont get your answers.

My job is copying rows from one table to another.

my code is like this:

InventSerial inventSerial

inventSerialCustom

while select inventSerial

{

inventSerialCustom.description = inventSerial.description

//

//

//

inventSerialCustom.insert();

}

Was this reply helpful? Yes No
Sohaib Cheema 49,438 User Group Leader on at

Like (1)

Report
Hi Muhammad,

You can use any of two approaches

By placing your code in posting classes

When a Transfer Order is posted, it goes through some classes and at end of processing of those classes you can add your code. You can also think to use post events after processing of certain methods. To get after which code, should be your customized code? You can turn on debugger to see stack trace.

By placing your code in destination table

When you post a transfer order, it changes/updates some values in Transfer Order header table, e.g. it may change status of Transfer Order. Etc. So, you can also write your code in update method of Transfer order header Table, based on some condition. I don’t think of any field named as posted in transfer order journal header. But if there is a field, you can write logic after super() of update() method e.g. as following

If(this.posted == noyes::yes)

{

//my custom code.

}

The first approach seems more concrete. Remaining you may choose any as per your needs and scenario.

Was this reply helpful? Yes No