Changes lost after checking-in menu items

(1) Share

Report

Posted on by Community Member

Hi all,

Recently, I am experiencing very strange behaviour with menu items and TFS.

More specifically, I made changes on several menu items and checked them in all at once. Unfortunately, the changes on half the menu items were lost. If I go on the menu items where I have lost the changes and view the history, the latest changeset is not listed. This leads me to believe that these menu items were NOT even checked in while the rest were for some reason or another. However, I did not receive any errors or warnings during the check-in.

Furthermore, if I check-out one of the menu items where I have lost the changes, do the changes again and check-in, sometimes it works.

Has anyone encountered this behaviour before? Why is this happening? I have only noticed this happening on menu items till now only.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Vilmos Kintera 46,149 on at

Like (0)

Report

I have not encountered this before, the only constant problem that TFS has is that it places a questionmark in some VS project files in front of the <xml tag, that break synchronization.

Do all entries have the Completed checkbox ticked under your Version control > Synchronization log in AX? If there are synch issues from the past, that could make your TFS check-out/check-in/synch unreliable and needs to be resolved.

Did anyone else check out those specific menu item? It is possible that during check-in AX is trying to show a popup of the code conflict resolve screen, which is not able to come up for some reason.

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

Like (0)

Report

Can you elaborate what happened? Even if the check-in failed for some reason, it wouldn't delete your changes in AX.

You added a tag named "synchronize" - does it mean that you also ran some synchronization that you didn't mention in text?

Also, look at one of objects that failed but you didn't manipulate it after the issue (if there is any). Look at the file in the repository folder; maybe your changes are there.

Was this reply helpful? Yes No
Suggested answer

Joris dG 17,775 on at

Like (0)

Report

Something to consider is the process that is happening. The AOT has to export an XPO to disk, then the TFS integration will check that XPO into TFS.

So, if for some reason the XPO didn't export, TFS looks at the XPO and says "there's no change" and won't add the object in the changeset. Next time you check-out, TFS won't get latest because it knows you have the XPO, but you still have your change sitting in the AOT. If you check-in again and the XPO is properly exported, it will of course get checked in that time. This would fit the scenario you're describing.

So the question may be, why is it not taking the XPO? If you consistently have this issue, can you try to explicitly "compile" the menu items before checking in? A compile should trigger the XPO export when an object is under source control.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Vilmos. I checked the synchronization log and there aren't any unprocessed entries.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Martin,

I wrote the "synchronize" tag by mistake. I inspected the file in the repository and it does not have my changes. I inspected the menu item in the AOT and still my changes are not there. However, a strange thing which happens is that if I do a compare between my layer (ISV) and the latest version from TFS, the compare tool is showing that they are different, highlighting the changes I made before the check-in in red. However, these changes are not visible in the AOT. I can't understand what is happening.

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

Like (0)

Report

Doesn't it mean that your changes are in TFS but not in AOT? Can you show us a picture?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Martin. Sorry, my reply was not very accurate.

If a compare is done on the machine where the development took place between the current version and the latest version from TFS, it shows that the changes are there in the current version. However, these changes are not reflected in the AOT.

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

Like (0)

Report

If you see changes in comparison with the TFS server but not in AOT, it very likely means that they are in the file in your repository folder. Please check it again.

Also note that I recently ran into a problem where AX comparison didn't show any changes between two versions in TFS, although they weren't identical. Comparison in Visual Studio showed them. Be careful if you compare changes in AX.

Was this reply helpful? Yes No
PA-22040759-0 6,194 on at

Like (0)

Report

I have had repeated issues with menu items where changes were lost during check-in because the submitted XPO didn't have the change.

It is like some property changes doesn't really "flag" the object as having been changed.

It is almost sure to happen when modifying a property like ConfigurationKey. In these cases I flip another property, like MultiSelect, back and forth before check-in and then AX considers the element as being changed.

It also happens a lot with the Parent property on Configuration Keys.

And it is a behavior that for me has started with R3.

Was this reply helpful? Yes No