Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are trying to use Mashup to integrate the visualizations with a third-party website, however when we are running we are getting error "require is not defined", we have tried to make the require.js file on the same location as the .html file but we ran into other errors.
What is the correct way to use the mashup in Qlik Sense Server? I have followed multiple videos but non worked well with me.
this is the connection to Qlik Sense in the .js file.
This usually happens when there are some issues with website and qlik being on different host
Do not try to move require.js , it should be loaded from qlik. as it may also have realtive paths inside of it, so it may other things.
Can u show the line where it refernces require.js ?
In mashup it will be in the html file in the head, in a script tag.
Also check in devloeper tools in the netowrk tab, and look for any issue in loading any of the resources.
and check console for errors, if the website is on different host, u need to add the host in the white list in the veritual proxy settings.
Thank you for the reply,
Here is the require.js file, actually we are running the website on the same qlik sense host server, I have also attached the network tab for the resources, and screenshot for the error in console.
Regards.
if u will look in the network tab, u will see require.js has 302 status
So it seems like authentication issue
What kind of authentication do u use ?
What did u set in the virtual proxy with prefix "vp" ?
we are using ticket method, and windows authentication method as "WindowsX", I was following a method that was working for someone however the same result didn't work on my side.
what the guy did was authenticating normally from "https://qlik/vp" and after generating the authentication token his website will work and require.js file will be defined, however on my side after I logged in, I still get the undefined require file.
ok, i see now in the cosole that u have CORS issue
try to add in the virtual proxy (vp) settings in the white list:
localhost
localhost:8080
and test, and please send screnshot of the console again
I have added localhost in the whitelist before, and I have added localhost:8080 just now, however still facing the same results in the console.
Regards.