You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With D365FO Version 10.0.13, enable the 'Ugrade three Jquery Component libraries' feature. Then using task recorder, have the 'capture screen shot' option turned on. Perform the steps to record a task and receive 'an unexpected client' errors when paging through the process of recording my steps. After stopping the recording, export the word document and none of the screen shots are capture. If the feature is disenable, everything works great.
I have not heard anything back on a solution or update. I will assume when it becomes mandatory Per April 2021 release and more clients experience the issue, something will finally be done.
Good news, Microsoft just informed me that they are going to release a fix within the platform update 41 (which is version 10.0.17 I believe).
Preview availability (PEAP) February 1, 2021 | Generally available (self-update) March 19, 2021 | Auto-update schedule (via LCS Update Settings) production start date April 2, 2021
Well this is good news, since I had originally opened a MS ticket back in Oct 20 and was then told they were not responsible and had to open an issue under github. Tried to push back because based upon the documentation, they have you creating an extension. I'm glad MS changed their minds.
With D365FO Version 10.0.13, enable the 'Ugrade three Jquery Component libraries' feature. Then using task recorder, have the 'capture screen shot' option turned on. Perform the steps to record a task and receive 'an unexpected client' errors when paging through the process of recording my steps. After stopping the recording, export the word document and none of the screen shots are capture. If the feature is disenable, everything works great.
See attached file
Issue 439 - JQuery Feature Enable Breaks Task Recorder Screen Shot option.docx
The text was updated successfully, but these errors were encountered: