mixed up AOT

(0) Share

Report

Posted on by CRSW

625

In our dev system we have a mismatch in the AOT. There is a Table in the AOT names TaxTransDetail_BE which should be a View and is a View on the SQL server.

How can this happen and more important how can I fix this?

Best regards

Chris

I have the same question (0)

All responses (7)

Answers (1)

André Arnaud de Cal... 301,148 Super User 2025 Season 2 on at

Like (0)

Report

Hi Chris,

Can you provide some more information? Do you know what happened to this environment? Did it work before?

Possibly add some screenshots to show what you mean by "should be a view"? Have you tried a full X++ compilation and CIL build? Then there after, you can run a full database sync and check if it solves the issue.

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

Hi

Yes the system worked before. I don't know what happend to it. Its a standard object still in the standard "Layer".

It just turned from view to table

In Test and Prod System it is fine. only in dev not

CIL and DB sync failes because of this object.

First pic. Not correct (Devsystem), second pic correct Test system

Was this reply helpful? Yes No
André Arnaud de Cal... 301,148 Super User 2025 Season 2 on at

Like (0)

Report

Hi Chris,

When reading your last reply, it may be the case that a database movement was performed from e.g. prod to this development environment. In case this move was done without moving the model store as well, there can be differences in object numbers that can cause this behavior. Can you check if there was indeed a database movement action?

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

there was no DB movement since at least 1 year. I checked the IDs in Modelstore Dev and Test. they are identical. because it is a standard object, never changed I didn't suppose anything else

Was this reply helpful? Yes No
André Arnaud de Cal... 301,148 Super User 2025 Season 2 on at

Like (0)

Report

Hi Chris,

It would be very hard now to guide you further. At least, something must have been changed, but you are not aware of it. For me, working with AX 2012 is too long ago to remember every single detail. PS. Did you already try a full compilation as I suggested in my first reply?

Was this reply helpful? Yes No
CRSW 625 on at

Like (1)

Report

Hi Andre

I am pretty sure nothing has been done because normally it's me doing this or one other developer. And he didn't do anything eather.

To stop discussion I will take DB from Prod to fix this. seems to be the fastest way

Thx

Was this reply helpful? Yes No
Verified answer

CRSW 625 on at

Like (0)

Report

Thx to all I just decided to do a copy from prod to fix everything(seems to be the fastest way)

Was this reply helpful? Yes No