Hello,

Thank you for the details and sample application you have provided.

At the time you return the custom customizations XDocument to XamDataGrid the FieldLayout that is out of the view is not created and this is the reason that the changes are not applied. In order to load customizations for layout that is not created yet, you should  modify the customizations logic you are using. In your MoveField method you are adding column attribute only for specific Fields, so the XamDataGrid does not know how to arrange  the fields that are not visible.

You can modify the DataGridColumnLogic.MoveColumn method to add default attribute values(column, row, etc.) for all of the fields, so the XamDataGrid can load the field positions correctly:

// Get the two fields (one as desired, one to which we will apply changes.)
XElement LoopApplyField = FindFieldInLayout(CurrentLayoutElement, LoopDesiredFieldName);
if (p_ColumnName != LoopDesiredFieldName )
{

    if (LoopApplyField.Attribute("column") == null)
    {
        if (p_ColumnPos == defaultPosition)
            defaultPosition++;
        // Get the two fields (one as desired, one to which we will apply changes.)
        LoopApplyField = FindFieldInLayout(CurrentLayoutElement, LoopDesiredFieldName);
        LoopApplyField.SetAttributeValue("column", defaultPosition.ToString());
        LoopApplyField.SetAttributeValue("row", "0");
        LoopApplyField.SetAttributeValue("rowSpan", "1");
        LoopApplyField.SetAttributeValue("columnSpan", "1");
        LoopApplyField.SetAttributeValue("isCollapsedInLayout", "false");
        defaultPosition++;
    }
}
else
{
    oldPosition = defaultPosition;
    LoopApplyField = FindFieldInLayout(CurrentLayoutElement, LoopDesiredFieldName);
    
    // Set the attribute to the desired value
    LoopApplyField.SetAttributeValue("column", p_ColumnPos.ToString());
    LoopApplyField.SetAttributeValue("row", "0");
    LoopApplyField.SetAttributeValue("rowSpan", "1");
    LoopApplyField.SetAttributeValue("columnSpan", "1");
    LoopApplyField.SetAttributeValue("isCollapsedInLayout", "false");
    defaultPosition = oldPosition;
}

I have modified the project you have attached to illustrate the suggested approach.

Please let me know if you require any further assistance regarding this matter.

Sincerely,
Zhivko
Entry Level Software Developer

Here is the main issue: Only certain fields are customizable.  IE the ones named "Movable" or whatever.  Think of this as a "delta" operation that keeps everything exactly as-is except for columns that are specifically identified.

All other columns must retain whatever default behavior is given to them by (1) the XamDataGrid implementation, as developed by Infragistics, and (2) by the current XAML markup that defines our data grid.

Given we want "default" behavior for layouts and columns as indicated by (1) and (2) above, it seems like a very bad idea for me to be "whacking" on all columns, whether "Movable" or not, in a manual/programmatic way as you are doing.  (Thereby hard-coding all sorts of things that should be coming from markup like the "row", "rowSpan", "columnSpan", etc.)  It will be a fragile solution that regularly breaks if/when the implementation of the XamDataGrid changes and as our XAML markup changes over time.

The theory behind the current design is that we extract the state of the grid, given (1) and (2), and we only adjust only the pieces we care about before sending the back the customizations.  Note that it starts with a call to "SaveCustomizations()" and ends with "LoadCustomizations()".  Your grid should be able to support the Loading of its own Saved customizations.

Moving forward, you had mentioned a timing issue (grid "not created yet").  Please tell me what event or property you are using to determine this.

While I understand your workaround, I'd prefer a slightly different one that preserves more of the "default" behaviors of the XamDataGrid, given (1) and (2).  Can you please tell me what happens in a "PreLoad" grid that triggers all the layouts to be "created" even the ones that are "out of view"?  I'm hoping that I can preemptively force that same thing to happen in a "Recycle" grid at a pre-determined moment of time, right before the customization logic is performed.

Hello David,

I have reviewed your post and asked a few other developers to look into this scenario. We are working on your issue in order to provide you the best solution.

I will follow up with our findings as soon as we are ready with our  investigation.

Thank you for your patience and understanding.

Sincerely,
Zhivko
Entry Level Software Developer

David,

Thank you for your reply. The issue has been since fixed internally and is now currently awaiting test. We will provide more details as they become available.

Thanks for getting them involved.  I don't know if you read it in an earlier post but I had also opened a support case, simply so I can tell the stakeholders that I had opened a support case (CAS-177679-F0K1C7) .

I'm eager to get a good work-around as soon as possible.  My original guess was that this would take three weeks or so.  Please let me know if you think things will move slower than that.

Thanks, David

Hello David,

To ensure that your issue will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 226687.  The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.

Please let me know if you need more information.

Sincerely,
Zhivko
Entry Level Software Developer