Kiran,

I know that there has been an issue that was addressed for the excel engine that resulted in a similar exception.  As such if you are still seeing this, you should test with the latest service release.  If you are using the latest service release and still see the issue then we would need an excel file that reproduces the exception.

Let me know if you have any questions with this matter.

Hello Kiran,

I created a sample project for you, where I used the exact same version as yours, and I wasn’t able to reproduce your issue. I attached the sample project and if it doesn’t satisfies all your needs feel free to modify it, so it reproduces your issue, and send it back to me for further investigation.

Looking forward for your reply.

Hi Stefan

Any updates pls.. We are waiting for the fix so taht we can release it to Production.

Thanks

-Kiran

Hello Kiran,

I have been looking into the modified sample and I can say that this behavior is expected and is by design. I can suggest you loop through the FilterRecords collection items and check whether they have conditions. This way you will be able to know how many active filter are applied to the XamDataGrid. You can do something like this:

int count = 0;
foreach (var item in xamDataGrid1.FieldLayouts[0].RecordFilters)
{
    if (item.Conditions.Count != 0)
    {
        count++;
    }
}
MessageBox.Show(count.ToString());

Hope this helps you.

Hi

  Thanks for the reply. I figured it out the same.

-Kiran

Hi

  We are facing lot of issues with the patch version you guys provided. We found these in Production & had to revert back (Took lot of heat from users). Pls provide me only excel fix. We don't want anyother changes.

I ahve attched the issues file. since I can attach only 200 MB. I wil raise one more post & attach another file.

thanks

-Kiran

Attached one more file

Thanks

-Kiran