Reason of this behavior is a sequence of applying multiple rules:
- When an App is created on RIM node, according to built-in Sync Rule "ResourcesToCentralNodes", this app is synced to Central Node.
- According to the modified Sync Rule "ResourcesToNonCentralNodes", this app is NOT synced to RIM Node.
- Because this app already exists on RIM Node, it is deleted from RIM Node because of step 2.
- The deletion is then synced back to Central Node according to "ResourcesToCentralNodes".
- 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:
Also one needs to communicate with users who are going to use RIM Node so that they are aware of this restriction(in example above, name all new Apps as "Dev*"). Otherwise it is still possible to create Ghost Apps.
- Disallow Sync from Central Node to RIM Node
- Allow certain type of Sync from Central Node to RIM Node. In example above, this "certain type" is defined by App Name.
To resolve this, follow these steps:
- Instead of modifying the built-in "ResourcesToNonCentralNodes" Sync Rule, simply disable it.
- Create a new Sync Rule to specifically define how syncing from Central to RIM node should work. It probably looks like this:
- 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.