-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Doesn't show the end of job pop-up and block the XrmToolbox app #225
Comments
Hi - I'm glad you like this tool 🥰 But that's bad... when to tool just locks everything. I'd like to find a way when / why that happens. Want to add a few screenshots here and there during the execution? |
Thank you very much ! I sent you more details by emails |
Thanks for more details! I believe this is "only" a window issue... I was now able to reproduce your issue: If I minimize the XrmToolBox while all updates are running when it is done, and it pings you and tries to open the window again, then the popup is behind. One way to solve this issue is too simple: Focus on XrmToolBox, hit space, or enter on the keyboard, and the default option will appear in the popup. Hopefully, this annoying solution helps you. |
Omg yes it works, never thought about trying that! Really good to know 😊
Thank you for your quick answer !
Have a great day !
|
Hello !
First of all, your tool is a life saver. It's been years I use it and I can't live without it :) Thank you !
Since few months, I have to use it on a weekly basis to do a field touch on more or less 7000 records.
It used to show a pop up at the end to warn me that the job is done and the number of records updated, but since the lasts updates it doesn't show the pop up anymore, but the app is still locked like when it expects me to close the pop up window to continue. I cannot click or close anything. There is no other XrmToolbox windows or hidden pop ups anywhere. Evertime I need to kill XrmToolbox to be able to use it again.
Let me know if I missed something.
Thank you !
The text was updated successfully, but these errors were encountered: