Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Accepted Solutions
Both links are broken for me, at the moment.
Here is a link:
QEXT files
When you save a mashup project from the Mashup editor, a QEXT file is automatically included in the project. A QEXT file is a JSON file, and contains all metadata required by the Mashup editor to recognize the mashup project. It is also required if you want to launch your mashup from Qlik Sense Desktop.
The QEXT file is automatically created by the Mashup editor. You need to manually add a QEXT file if you have created a mashup project not using the Mashup editor, and you want it to be accessible from the Mashup editor.
The QEXT file extension must be in lower case letters, for example MyMashup.qext.
Example: QEXT file content
{ "type": "mashup", "name": "MyMashup", "allowPosition": true }
WBL files
The Workbench load file (WBL) is used by the Mashup editor, and lists the names of all files included in the mashup project. When you save a mashup project from the Mashup editor, a WBL file is automatically included in the project.
Example: WBL file content
MyMashup.qext; MyMashup.html; MyMashup.js
I was under the impression WBL file was required to import an extension
I guess WBL isn't required to import extension -- only needed to import a mashup am I right?
I see the WBL file is autogenerated using the dev-hub editor...
EDIT
After an experiment on my Qlik Sense 3.1 SR3 (qliksenseserver:10.7.2), it looks like WBL file is not required for import? Not for extensions, not for mashups?
Maybe the WBL is only required for the dev-hub editor to work? So if I prefer my own IDE I don't need the WBL file?
