Dependency check won't let me delete template -- but it's dependent only on itself?
I'm stuck on something I think must be a bug, but perhaps I am just doing it wrongly. I am on 7.0.8, and have a template that generates a LOT of LLD items and triggers (typical about 1700 of each in my current case).
The LLD itself is also populating fields view trapper/sender, so it is important that the triggers not fire if this LLD process breaks for some reason (it's accessing another system which may be down). So each trigger looks like this:
And this is defined as a regular trigger (not one generated by LLD) in the same template:
If I try to unlink-and-clear this template it fails, calling out the dependency
That trigger above is the only dependency. Now admittedly it is tagged to a LOT of triggers, but it's the same one.
Shouldn't you be able to unlink a template when triggers it generates refer to it's own trigger?
I can delete the host itself. But if I recreate it with the same template it fails the same way again (the actual trigger it flags is random).
Am I missing something or is this just broken?
The LLD itself is also populating fields view trapper/sender, so it is important that the triggers not fire if this LLD process breaks for some reason (it's accessing another system which may be down). So each trigger looks like this:
And this is defined as a regular trigger (not one generated by LLD) in the same template:
If I try to unlink-and-clear this template it fails, calling out the dependency
That trigger above is the only dependency. Now admittedly it is tagged to a LOT of triggers, but it's the same one.
Shouldn't you be able to unlink a template when triggers it generates refer to it's own trigger?
I can delete the host itself. But if I recreate it with the same template it fails the same way again (the actual trigger it flags is random).
Am I missing something or is this just broken?