Skip to content

Instantly share code, notes, and snippets.

Load this data:

LOAD DUAL(t,n) INLINE [ t,n A,1 B,2 C,3];

Select "A", create a bookmark

In Qlik: Applying selection manually in some order; A later selection "trumps" an earlier selection i.e. selection on field at time t, will be trumped by subsequent selection on field at time t+1

But when saving a selection with Qlik bookmark The order that the selection appears in the Selection toolbar, will be consistent with load order, that is, the order shown in a Filter pane added to your Qlik app; whose field is the magic: $Field , and remove any other Sort Order (see resulting message "will show Load Order")

//----------------------------------------------------------v
export function DrawableGroup(options?: any): ClassDecorator {
//----------v
return <ClassDecorator>function (target) {
target.prototype.getDrawableGroup = function () {
//...
javascript: (function () { var jsCode = document.createElement('script'); jsCode.setAttribute('src', 'https://rawgit.com/theredpea/d08d5918a8c88889dfa26ad72dd17140/raw/60c7294ee9e6fa42daec318465b460c6e320dbf0/adapting_showObjectIds.js'); document.body.appendChild(jsCode); }());
curl -u theredpea:USER_PASSWORD "https://api.github.com/repos/OWNER/REPO/commits?author=theredpea&since=2018-11-10&sha=feature/GeneralUiEnhancements"c
curl -H "Authorization: token AUTH_TOKEN_GENERATED_AT_GITHUB" "https://api.github.com/repos/OWNER/REPO/commits?author=theredpea&since=2018-11-10&sha=feature/GeneralUiEnhancements"
function x(a, b) {
function c(c) {
a.model.isCancelled || (a.layout = c,
b.setLayout(c, a.options))
}
/////////////////////////////////
function d(a) {
a && (b.model && g(b.model),
e.empty = r(a.markdown) && !d,
e.html = w.trustAsHtml(h.toHTML(a.markdown, a, !0)),
e.direction = this.view.options.direction,
e.textDirection = l.getAutoOrAlternativeDirection(a.markdown),
e.markdown = a.markdown,
function syncSheet(app, def, list) {
extend(def.qProperty.qMetaDef, blueprintTag)
if (list.indexOf(def.qProperty.qInfo.qId) === -1) {
return app.createObject(def.qProperty).then(function(handle) {
return handle.setFullPropertyTree(def).then(function() { return handle.publish(); });
})
} else {
return app.getObject(def.qProperty.qInfo.qId).then(function(handle) {
return handle.setFullPropertyTree(def).then(function() { return handle.publish(); });

Architeqt notes

  • blueprintProp
    • only if you set up your Qlik to use this custom prop; I think my customer/client did not use that option;
    • and only if you query the endpoint to get the list of "blueprint" apps
    • distinction: blueprintProp (an app can be made into a blueprint; i.e. is considered a "template"); vs blueprint (the actual JSON object, mostly serializeapp results) /*
    • Nate says: The '@' is the tip that the config.qmc.blueprintProp (whose default value is 'Blueprint')
    • is a Qlik Custom Property which is created in the QMC
  • So it means if (all can be checked in QMC)