Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Mashup will not render

Hello Community,

I am trying to develop a Qliksense mashup with AngularJS and am able to retrieve the object and all of its information correctly (ss of result of app.getobject() attached).

The object from the get does have a qHyperCube property which appears to be populated, however, at some point when the object is trying to render on the webpage, I run into the follow error:

TypeError: Cannot read property 'qHyperCube' of undefined

I've also tried app.createVisualization to create a new simple object on the spot as well as several other objects in my application, however, these all run into the same issue.

This application is hosted on an external server.

The scripts being used are the various angular scripts I have (angular-material, angular-messages, angular-ui-router, etc), https://server_name/resources/js/external/requirejs/require.js, and app.js.

Also attaching a SS of what the issue looks like.

Has anyone run into this issue before or have suggestions on how to resolve it?

Thank you,

Damon

1 Solution

Accepted Solutions
Francis_Kabinoff
Former Employee
Former Employee

Hey Damon,

Some time last year I tried building a mashup with angular-material and remember I had issues and abandoned it. I forget what the issue was to be honest, or what errors it was causing, but it might be worth quickly testing if removing angular-material makes any impact.

View solution in original post

2 Replies
Francis_Kabinoff
Former Employee
Former Employee

Hey Damon,

Some time last year I tried building a mashup with angular-material and remember I had issues and abandoned it. I forget what the issue was to be honest, or what errors it was causing, but it might be worth quickly testing if removing angular-material makes any impact.

Not applicable
Author

Thanks for the reply! This was the issue.