-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled exception upon showing Both Names in result view #963
Comments
I thought I had fixed that type of issues... 😣 Can you give me more info? Is FXB closed after the error message? Does this error appear always, with other queries as well? Can you share your settings for FXB?
|
Hi, There is always something unnoticed - Murphy's law ;-) The query I open from CRM, where I prepared it (menu Open - Open View...). FXB is not closed automatically after displaying the error message, but I get a choice: either to Continue or to End. If I choose to End, FXB is closed after few dialogs, as well as XrmToolBox. If I choose Continue the error message disappears and I regain control of FXB. Good point rappen: the error doesn't appear with other views! So someting bad in this view only... The settings attached. With best regards |
I can now reproduce the issue! |
Thank you rappen! |
…o be sure Display is proper index
You may test this fix now 🤓 |
Yes, that works 👍 I'm not getting the error anymore, even when I do switching "Both Names" on and off. Many thanks for your fast and great support rappen! |
Hi,
I've just updated FetchXML to version 1.2023.8.2 and opened there a previously prepared view. When I tick the option Appearance - Both Names in the result view, it immediatelly shows an exception (bellow). When I leave Both Names unticked (and keep only Freindly Names on), then it works normally, without exception.
The exception text (attached, with screenshots) tells that the property DisplayIndex of DataGridViewColumn control must be smaller than the number of columns. Real value was 85.
Would you advise please?
Best rergards
Veroslav
FetchXML unhandled exception.docx
The text was updated successfully, but these errors were encountered: