Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
_jespers_
Partner - Creator II
Partner - Creator II

Error with Field API

I get an error while using getData() with the Field API.

I have followed the example given on https://help.qlik.com/en-US/sense-developer/September2017/Subsystems/APIs/Content/CapabilityAPIs/Fie...

The error shows up as soon as I do any kind of selection on a field.

Even this simple example gives the error:

define( [

        "qlik",

        "jquery",

        "text!./template.html"

    ],

    function ( qlik, $, template ) {

        "use strict";

        var app = qlik.currApp(this);

        return {

            template: template,

            definition: {

                type: "items",

                component: "accordion",

                   items: {

                    dimensions: {

                        uses: "dimensions"

                    }

                }

            },

            support: {

                snapshot: true,

                export: true,

                exportData: false

            },

            paint: function () {

                var field = app.field("Dim1").getData();

                return qlik.Promise.resolve();

            },

            controller: ['$scope', function ( $scope ) {

            }]

        };

    } );

This is the error given:

field-issue.PNG

To reproduce the error:

1. I use the Qlik default data in this example ( CTRL + 00)

2. Add the extension to a sheet

3. Add a dimension to the extension

4. Add a filter pane with any dimension

5. Make a selection in the filter pane

Any idea what is causing this issue?

1 Solution

Accepted Solutions
Aiham_Azmeh
Employee
Employee

Hi erik.wetterberg‌, jesper.snihs‌,

     It's a known bug, already reported and fixed in the latest release (I think nov. release).

br,

View solution in original post

3 Replies
ErikWetterberg

A bug?? Have you tried reporting it?

Erik Wetterberg

Aiham_Azmeh
Employee
Employee

Hi erik.wetterberg‌, jesper.snihs‌,

     It's a known bug, already reported and fixed in the latest release (I think nov. release).

br,

_jespers_
Partner - Creator II
Partner - Creator II
Author

Thanks for the answer, aaz

Then I will test this when the latest release comes out