Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Any ideas? On Demand is the main use case for us.
error
cmbsreporting.limekilnre.com:4993/api/v1/ondemand/requests:1 POST https://cmbsreporting.limekilnre.com:4993/api/v1/ondemand/requests 500 (Internal Server Error)
cmbs.limekilnre.com/:1 Access to XMLHttpRequest at
'https://cmbsreporting.limekilnre.com:4993/api/v1/ondemand/requests' from origin 'https://cmbs.limekilnre.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Unfortunately there is a bug specifically around the "CORS" message that has been already identified and scheduled for a patch resolution soon.
The patch will be available in the Qlik Sense Feb 2019 SR 1 release that is scheduled for a couple week after the GA (generally available) which is due any day now.
Please see the following for more details on the fix and the upcoming patch.
https://support.qlik.com/articles/000062325
Unfortunately there is a bug specifically around the "CORS" message that has been already identified and scheduled for a patch resolution soon.
The patch will be available in the Qlik Sense Feb 2019 SR 1 release that is scheduled for a couple week after the GA (generally available) which is due any day now.
Please see the following for more details on the fix and the upcoming patch.
https://support.qlik.com/articles/000062325
Do you know if this can be made to work off of Desktop for the time being as a workaround?
Has the release which fixes CORS issue been published and if not, is there a preview for it as well?
Frank any shot on finding out when this fix is coming?
The fix is coming in either QS SR 1 or QS April release.
The release timing is completely in the realm of R&D.
HI,
Was this fix applied for the April 2019 release? We appear to be having a similar issue and are on April 2019.
dan
We have a new finding - if the April 2019 release did not 'apparently' fix this issue. I will be writing an article about this later today. The answer is separate from the fix included in April 2019 NP and applies to specific filter conflicts.
In the meantime, try removing any NPrinting report filters from the filters section of your NPrinting report in question.
Then try the On Demand report again. Does it work?
If you select a Qlik Sense dimension value in the Sense hub for the report you are trying to produce that is not of the same dimension or dimensions used as your NP report filter, then a conflict occurs resulting in a Request failed message when generating the report.
Check this out and let us know the results.
Article created.
How to manage Qlik Sense NPrinting On Demand "Request Failed" message
See https://support.qlik.com/articles/000074356