topic Re: Fresh copy of basic Angular visualization issue in Integration, Extension & APIs

Fresh copy of basic Angular visualization issue

_jespers_ — Fri, 15 Dec 2017 10:13:32 GMT

Hi,

I have an issue with my extension when reloading the URL in edit mode.

This issue even happens for a fresh copy of the basic angular visualization.

So the code for the issue is the basic template:

define( ["qlik", "text!./template.html"],
    function ( qlik, template ) {

        return {
            template: template,
            support: {
                snapshot: true,
                export: true,
                exportData: false
            },
            paint: function () {
                return qlik.Promise.resolve();
            },
            controller: ['$scope', function ( $scope ) {
                //add your rendering code here
                $scope.html = "Hello World";
            }]
        };

    } );

And when I add the extension to the sheet it looks like this:

But when I refresh the page in edit mode it looks like this:

It says "Invalid visualization - Visualization could not be found on the server: 'name_of_extension'"

But if I leave edit mode and refresh the page, it works fine:

And the issue will reappear if I enter edit mode again and refresh (as long as I refresh the page outside edit mode it works fine)

Any idea what can be the cause of this?

Regards

Jesper

Re: Fresh copy of basic Angular visualization issue

ErikWetterberg — Fri, 15 Dec 2017 11:05:18 GMT

Looks very much like a bug..What do you say aaz‌ ??

Erik

Re: Fresh copy of basic Angular visualization issue

Ann-Louise-Andersson — Fri, 15 Dec 2017 11:38:53 GMT

Hello jesper.snihs,

I can't reproduce this issue. What version of Qlik Sense do you have?

GIF:

Regards,

Ann-Louise

Re: Fresh copy of basic Angular visualization issue

_jespers_ — Fri, 15 Dec 2017 14:50:40 GMT

Hi Ann-Louise,

Strange and too bad you couldn't reproduce the issue.

I'm using Sense November 2017 Patch 1.

Re: Fresh copy of basic Angular visualization issue

Aiham_Azmeh — Mon, 18 Dec 2017 07:09:30 GMT

Hi erik.wetterberg‌,

Yes, this is an already reported bug and fixed in the next Qlik Sense release -