X++ or SQL

(0) Share

Report

Posted on by add

Hello guys,

I have to move some data from one field to another in the same table and also from one table to another.

And I was wondering which is the best way. Should I use X++ with the update_recordset and other such commands or is it better to do it directly with SQL from SQL Server Management Studio. Is there any difference at all? What is the best practice?

Best Regards!

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

Martin Dráb 236,118 Most Valuable Professional on at

Like (0)

Report

RE: X++ or SQL

Do you want somebody to have direct access to production database and run some scripts there? The usual answer is "no", therefore people usually write data update scripts in X++, save them to version control together with other code and metadata (such as the new field into which you want to migrate the data) and test and deploy them in the same way as all other changes.

Was this reply helpful? Yes No
Verified answer

Vilmos Kintera 46,149 on at

Like (1)

Report

RE: X++ or SQL

You cannot do this in SQL Server, AX maintains unique record identifiers (RecId and RecVersion) and many other fields from the kernel, which you cannot correctly generate using SQL.

That means yes, you need to build the code in AX. If this is a repeat task, you could utilize the Data Export Import Framework where you would create a custom entity for this copy routine. If it is a one-off task, then just simply do it in a Job.

Was this reply helpful? Yes No
add on at

Like (0)

Report

RE: X++ or SQL

I need to do it in production.

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

Like (0)

Report

RE: X++ or SQL

Are we talking just about some development environment, or do you need to do it in production?

Was this reply helpful? Yes No