Skip to content
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

JQuery Feature Enable breaks Task Recorder Screen Shot Option #20

Open
kmsorrentino opened this issue Oct 29, 2020 · 4 comments
Open

JQuery Feature Enable breaks Task Recorder Screen Shot Option #20

kmsorrentino opened this issue Oct 29, 2020 · 4 comments

Comments

@kmsorrentino
Copy link

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

@pwvanengelen
Copy link

Same here. Any solution or update on this issue? This feature will become mandatory as per the April 2021 release.

@kmsorrentino
Copy link
Author

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.

@pwvanengelen
Copy link

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

@kmsorrentino
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants