915
Hi,
we have changes sales price for few items and run N job 1020 , but it took around a day to complete the downloading. Is there any option with which we can only send updated records instead of system read all items and delete/insert in channel db?
Thanks.
*This post is locked for comments
Yes you rights, it works for me too. Thanks
Hello All, below linked helped me to sort out this issue.
Yes i got same issue here,
My environment is AX 2012 R3 CU 10 and SQL tracking is On. Running Jobs 1020 or 1050 on Retail > Periodic > Data distribution > Distribution schedule. or Retail > Setup > Retail scheduler > Channel integration> Channel database
all above have same issue which is take along time to complete.
approximally 2 hours or more.
In my opinions, It seems all jobs that regarding product, is take a long time to complete, but why jobs 1050 is same.
Is there anyone know how to fixed this.
Regards
Dwipa
Hi,
this case is also happen in my client when using CU 10 when execute job 1020 and the other job. But it doesn't take a day to complete, instead of 2 hours. This never happens in CU8 (CU8 only takes several minutes to complete). It seems that the job process all the data, instead only process the delta. So it takes a long time to complete the job.
yes even with no price change if I run this job it took that long and show same number of rows affected.
Thank you Sergey, you are right in R3 there are only two jobs i.e. download/upload.
about version details, its R3 CU 10
I have tried with the option [sql change tracking enabled with 2days against CDX] you have mentioned but could not get desire results.
e.g. I have changed price for one item in AX and then run job 1020 , it took around one day to complete this task. When I goto download session inquiry there I can see million of rows are get affected.
I am then not sure why you are talking about N Jobs in context of R3 - as I remember those types of jobs existed in R2 only and R3 has just Jobs (without N or A). So, as I asked earlier would be good to know what exactly build CU you are using.
Also, please tell me how exactly you validated that the delta is not sent, please note that first time you execute a job it will send all the data (just because it is FIRST time and nothing was sent yet) but if you execute the job second, 3rd, ... time it will send delta only. So, I would like to see how exactly you validated that the delta was not sent for not Initial (first time) sync.
Please also note that CDX uses SQL Change Tracking to be able to send the delta, the SQL Feature itself has Retention Period set to a number of days, what it means for you:
if let's say that period is 2 days but you execute the job every 3 days then you will never have delta - you will always experience Full Sync - please check that setting in your SQL Server Management Studio and then "map" it to a frequency your jobs run with, probably this will explain why you are experiencing Full Sync instead of Delta Sync.
There is no A job in R3 , is there any alternate available of A jobs in R3?
If You'll Run N-Jobs (Normal) it will send all the date without filtering. If you want to transfer only changes what you made run A-Jobs (Actions).
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
