-
Notifications
You must be signed in to change notification settings - Fork 18
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
export to excel not working after upgradation #20
Comments
Hi, try to upgrade to one of the two latest versions. |
Hi, Thanks a lot for the quick reply. |
If you are using one the two latest extension versions the Excel export should work fine with Chrome. I only test it with Chrome.
|
Thanking you for the prompt response.
I have done as you have suggested and got below error:
This plugin is unsupported and deprecated, use instead angularjs $injector
load @ /resources/assets/qvangular/qvangular-injector-require-plugin.js:27
Kindly let me know what needs to be done.
Thanks
…On Tue, Jan 15, 2019 at 12:32 PM Ivan Felipe Asensio < ***@***.***> wrote:
If you are using one the two latest extension versions the Excel export
should work fine with Chrome. I only test it with Chrome.
Could you do this:
- open QS with Chrome and click F12
- try to export to Excel and take a look at the browser console on the
right
- is there any error message?
regards
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ApgStPv3VufdwI-TRGYBK0Fe0GJu4Zm8ks5vDbw2gaJpZM4Z3QFZ>
.
|
OK, tested |
Some changed in the way you ask about the navigator vendor, in the case of Google Chrome, no changes for the rest of vendors. Not sure about if it's due to a Qlik update or a Chrome update. Anyway it's now fixed the old and latest version of the extension. |
Thanks a lot!!.. |
After upgrading from Nov 2017 to Sept 2018, export to excel is not working. Please let me know in case of any solutions
The text was updated successfully, but these errors were encountered: