Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Qlik Sense Enterprise: Be careful when editing Sync Rules as it may cause unexpected results

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Andre_Sostizzo
Digital Support
Digital Support

Qlik Sense Enterprise: Be careful when editing Sync Rules as it may cause unexpected results

Last Update:

Nov 11, 2021 9:55:21 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 3, 2016 6:28:56 PM

Consider this scenario:

  • There are two nodes: one Central Node and one RIM Node(called "Dev")
  • The user wants one-way Sync. That is:
    • When an App is created on the Central Node, it is not synced with RIM Node
    • When an App is created on RIM Node, it is synced with Central Node
  • User modifies the built-in "ResourcesToNonCentralNodes" Sync Rule to add "and node.name!="Dev"". The idea is to exclude RIM Node from this rule, which syncs resources from Central Node to Non-Central Nodes.

    User-added image

  • Results of this modification are rather unexpected:
    • When an App is created on the Central Node, it is not synced with RIM Node -- as expected
    • When an App is created on RIM Node, it appears on the Central Node -- as expected
    • But this App cannot be opened on either the Central Node or RIM Node. It shows this error:

      User-added image
    • Furthermore, this App eventually disappears from both nodes. Although it is still shown in Apps list on QMC but cannot be found anywhere else. It becomes a "Ghost App".

 

Cause:


The reason for this behaviour is a sequence of applying multiple rules:

  1. When an App is created on RIM node, according to built-in Sync Rule "ResourcesToCentralNodes", this app is synced to Central Node.
  2. According to the modified Sync Rule "ResourcesToNonCentralNodes", this app is NOT synced to RIM Node.
  3. Because this app already exists on RIM Node, it is deleted from RIM Node because of step 2.
  4. The deletion is then synced back to Central Node according to "ResourcesToCentralNodes".
  5. The final result is this app is deleted from both Nodes. Even though the icons may still be shown, users cannot open them because Qlik Sense cannot find it.

In order to break this loop, a new Sync Rule needs to be designed to do these two things simultaneously:

  • Disallow Sync from Central Node to RIM Node
  • Allow certain type of Sync from Central Node to RIM Node. In the example above, this "certain type" is defined by App Name.

Also one needs to communicate with users who are going to use RIM Node so that they are aware of this restriction (in the example above, name all new Apps as "Dev*"). Otherwise, it is still possible to create Ghost Apps.

 

Resolution


To resolve this, follow these steps:

  1. Instead of modifying the built-in "ResourcesToNonCentralNodes" Sync Rule, simply disable it.
  2. Create a new Sync Rule to specifically define how syncing from Central to RIM node should work. It probably looks like this:

    User-added image
  3. The important point here is, Sync Rule should not stop Syncing to one node completely. There should be some rules(in this example, App Name starts with "Dev*") to allow syncing to this node.
Labels (1)
Version history
Last update:
‎2021-11-11 09:55 AM
Updated by: