Hi Team,In our product, we are using Infragistics NetAdvantage 2013.2, and now we're looking for an upgrade to the latest version, NetAdvantage 2023.1. We observed that the IsGroupBy field was not found in Version 2023. Could you please someone help on this to use the IsGroupBy field?Test Code Snippet for ref:
Hello Mahender,
I am glad that the suggested approach worked.
Regarding your subsequent question, I am afraid I am not familiar with this DataPresenter.Fakes namespace as well as the ShimField class, neither the testing framework/setup.
According to our API Reference Guide for the Ultimate UI for WPF product here, there is no such namespace as part of the product.
Could you please clarify if this setup is related to an additional Testing Framework which your app is depending on, which would be most likely retired, as is the NetAdvantage?
As mentioned, please, keep in mind that it is possible that not every single API has its exact equivalent in the Ultimate UI for WPF most recent versions, given the huge gap and the general difference between the NetAdvangate and WPF products.
While manual changes will most likely be needed, and not everything may be resolved by it, a useful resource you might consider is the Version Utility which allows you to easily upgrade existing solutions. Please, check out this page, which outlines all details regarding its usage.
Best regards, Bozhidara Pachilova
Thanks, Bozhidara, the mentioned approach has worked for me!!!We're now experiencing compilation difficulties because unit test cases are failing, and I noticed several of the properties in class ShimField are missing information. Could you please look at the screenshot below and assist me in locating equivalent properties?
Thank you for posting to Infragistics Community!
Please, note that the NetAdvantage product does not exist under this name anymore. I believe you are referring to Ultimate UI for WPF in this case, aren’t you?
Anyway, I have been looking into your question and what I can say is that upgrading from 10 versions back would be quite the huge gap and it is expected that the API has undergone some changes.
Regarding the creation of the custom FieldChooser’s FieldFilter, as far as I understand the provided code-snippet and the predicate, this particular filter should only include fields, not field groups. Please, do elaborate further in case this assumption is not correct.
More about Field Grouping in the current versions could be read in this topic of our documentation.
As you can read, field groups are separate objects of the FieldGroup Class.
Now, looking at the current FieldChooserFilter class and the Filter predicate API, the latter’s type is Predicate<FieldItem>.
The FieldItem is an abstract base class for both Field and FieldGroup. Therefore, I believe an equivalent code to what used to be back in version 13, would be the following:
Filter = f => f.GetType() != typeof(FieldGroup) // etc..
Please, check out this approach on your side and let me know if it works.
If you require any further information, please, let me know.
Best regards, Bozhidara Pachilova Associate Software Developer