Hi,  

I am now using 2010.03 for a different project and just wondering is this fix is already in this version?

Thanks,

Muthu

Any update on nmuthu's questions? I do not use customization but I have the similar problems with Field.ActualPosition.Column values. It has the value that does not correspond to real UI visible position after moving columns via drag&dropping.

Thanks, Alex.

Thanks Guys!

Are they any workaround availabe in current version inorder for me to move the columns in code and save customizations.

In otherwords what are my options to rearrnage the columns from the scratch. Can I  remove the FieldLayout and add one?

I try setting Column and Row to achieve the behavior however when saving customization the position information is not retained. It retained only when I do drag and drop.

Or until we have the fix I am not advised to programatically move the columns around?

Please find attached is my use case and advise.

Muthu

This is already submitted as an issue and is in development. I cannot say when it will be resolved.

This is caused because, the XamDataGrid keeps track of the user actions in respect to customizations. When the fields are moved in procedural code, this cannot be reflected anymore.

As I said, we are currently looking for a way to change this.

Any update on this please?

Also in which release version the fix for the issue "drag/drop  or LoadCustomizations causing the Fields.Move to not to work" would be avaialbe

Thanks.