I have a problem in the XamSpreadsheet regarding dropdowns. I created a small prototype to reproduce the problem. Both, the prototype and the excel-file that needs to be loaded into the application I put as an attachement to this post.
Steps in Excel:
Open the dropdown in any Cell of Column B:
Steps in the sample-WPF-program with the XamSpreadsheet /community/cfs-file/__key/communityserver-discussions-components-files/1041/SpreadsheetMinimalPrototype.zip :
Sample-Configuration in the Excel-Attachment (already done, just for informational purposes /community/cfs-file/__key/communityserver-discussions-components-files/1041/DropdownExample.xlsx):
Column A with 500 Entries
Select column B (or a single cell) -> Data -> DataValidation (under Data Tools) -> Settings ->
So my question is now: Why is it showing the blank entries in the XamSpreadsheet-Dropdown, that I configured to be ignored? How can I remove them from the dropdown-list to make the dropdown usable?
Thanks!
Hello Tomas,
I have been investigating into the behavior you are seeing, and I have reproduced it both in the version of Infragistics for WPF 2019.2 that you are using and the latest version of 2019.2. It appears that the ListDataValidationRule that is brought into the WPF Workbook object is not respecting the value of the “Ignore Blank” in Excel, and as such, all of the blank values are going into the drop-down.
This appears to be a defect with the Infragistics Excel Engine, and as such I have asked our development teams to examine it further. To ensure this receives attention I have logged this behavior in our internal tracking systems with a development ID of 271473. I have also created a private support case for you that I will be linking to this development issue so that you may be notified of a fix when it becomes available. This case has an ID of CAS-209530-F1Y2R1 and you can access this support case after signing into your account on the Infragistics website, here: https://ko.infragistics.com/my-account/support-activity.
Please let me know if you have any other questions or concerns on this matter.
Hello Andrew,
Thanks for analysis. This problem for us causing huge performance impact since we usually have 1 million rows selected in rule since we are not sure how many rows we need to setup in advance. Usually row count may vary between few lines to over 100 000 lines. I am hoping this problem gets resolved with upcoming release since it is a bit of blocker for our new User Story to be implemented which is now in progress already.