Microsoft Dynamics AX (Archived)

AOT Query range(ModifiedDateTime field)is not reflecting on all the servers

(0) Share

Report

Posted on by Manikanda Gopal

258

Hi All,

I have three AOS server configuration(AX2012 R3) where the query range is nor reflecting properly.

AOS1(Batch server)
AOS2
AOS3(TFS enabled)

I have CustTable and custom AOT query. It was working fine for a scenario when(enabled the modifieddatetime property of CustTable and added some date time range in my custom AOT query).
For other scenario i want to test by disabling the CustTable "modifieddatetime" property and it was worked perfectly.
Now i have enabled the modifieddatetime property again and trying to add the modifieddatetime range into my custom query but i could not do the same.

Below are the steps i have tried.

1) Stopped aos1 and aos2.
2) Enabled CustTable modifieddatetime property on table level and sync
3) Restored the query and deleted the fields from CustTable datasource re-selected again.
4) Added the query range "modifieddatetime" into the custom query.
5) Compiled the query and started the remaining services.

When i am checking the query range in ASO1 it is not set properly. Where it is looking fine on AOS2 and AOS3.

Please refer the below screenshot.

When i am selecting the modifieddatetime range from the field lookup its always setting as dEL_ModifiedTime
Tried the same steps by importing the query XOP manually but still no luck.

I have tried to access the AOT query through job and added the range to the modifieddatetime field. When i am prating the query into string it is pointing the del_modifiedTime instead of modifieddatetime.

I have followed the same steps on AOS1, where as AOS2 and AOS3 is down. It was setting properly on first time. But It wont when i am re-opening the ax.
Deleted the AUC file and tried, Still no luck.

Note: I am not able to find the del_modifiedTime field in sql. I am able access the both the fields(del_modifiedTime, modifieddatetime) from the AOT job.

Am i doing any mistake here? Please share your thoughts.
My batch jobs are getting failed because the range is not setting properly on batch server. After some times the same problem will occur on remaining two server.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

It sounds like you're developing in production, which is extremely risky. You get all sort of weird issues when things are not deployed consistently, you apply changes without any testing, you may block the whole system, development-enabled environments have worse performance and so on... Please don't risk your clients' critical business system and do development in a development environment, then test your changes and deploy them using a more reasonable process.

Anyway, you're trying to use a wrong field - you should use ModifiedDateTime instead of DEL_ModifiedTime. In fact, you shouldn't use any fields prefixed with DEL_. They're considered deleted; they exist there only to allow data migration to the new fields when upgrading to AX 2012.

Was this reply helpful? Yes No
Manikanda Gopal 258 on at

Like (0)

Report

Hi Martin,

Thanks for reply.

FYI, I am working on test environment.

Even selecting a modifiedDateTime field from lookup refereeing always dEL_modifiedtime. Is ther anyway to solve this issue?

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

Like (0)

Report

It's better than developing in production, but it's still no place for development and it means that you deploy changes to production from your development environment without testing in a test environment (because what you call a test environment is actually your development environment).

I'm sorry, but I don't understand your statement "Even selecting a modifiedDateTime field from lookup refereeing always dEL_modifiedtime". Please elaborate.

Was this reply helpful? Yes No
Manikanda Gopal 258 on at

Like (0)

Report

Hi Martin,

I have created a new range in the query. I was able to see the modifiedDateTime in the field lookup. When I am selecting modifiedDateTime from the field lookup its always pointing to the dEL_modifiedtime field instead of modifiedDateTime, also the query range name is changing as "dEL_Modifiedtime". Please refer the below screenshots.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Since it's working in your test environment, just do a proper deployment from test to prod and it will work in prod as well.

Developing in prod will just mess up your system.

Was this reply helpful? Yes No
Manikanda Gopal 258 on at

Like (0)

Report

Hi Nikolaos, I am facing this issue on my Test environment and its working as well.

Was this reply helpful? Yes No
Manikanda Gopal 258 on at

Like (0)

Report

Please ignore my previous post. I am facing this issue on my Test environment and its not working.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (1)

Report

By the way, since you said you have been switching the "ModifiedTime" property forth and back, and experiencing strange issues after that - I suggest you do a proper build in the environment where you are developing.

This means restarting the AOS and doing a full compile and database synchronization. Maybe then the selection for the criteria field starts working again.

In general I recommend setting up an automated nightly build in your development environment. And just like Martin, I strongly advice you to develop in a development environment. Not in test, and never in production!

Was this reply helpful? Yes No
Manikanda Gopal 258 on at

Like (0)

Report

Thanks for your suggestion Nikolaos.

Was this reply helpful? Yes No