AW: Deleting all tags - expected behaviour?

Michael Neumann mn at
Mon Nov 6 04:24:24 EST 2017

Take care – there are some bugfixes …. e.g. with the npm version 1.1.1 it will not work

Von: Users [mailto:users-bounces at] Im Auftrag von Dan Morphis
Gesendet: Mittwoch, 18. Oktober 2017 19:00
An: Community support for GenieACS users <users at>
Betreff: Re: Deleting all tags - expected behaviour?

Try adding a commit() after the delete.

declare(“Tags.*”, null, {value: false});
declare(“Tags.some_new_tag”, null, {value: true});

On Tue, Oct 17, 2017 at 6:22 PM, David White <david.white at<mailto:david.white at>> wrote:

Hi there,
         Can anyone please confirm the expected behaviour here.

I have a provision where I’m trying to delete all tags then apply a tag.

I would expect the following to work (but it doesn’t)

declare(“Tags.*”, null, {value: false});
declare(“Tags.some_new_tag”, null, {value: true})

It removes all tags, but doesn’t apply the new tag. If I do this manually and specify each tag to remove, then add a tag - it works.


David White

The contents of this email and any attachments are confidential and may be privileged.  If you are not the intended recipient, you may not use, copy or disclose this email or its attachments.  Please notify the sender immediately by e-mail if you have received this e-mail in error and delete both emails from your system.  It is your responsibility to check this email and any attachments for viruses or other harmful code before opening or sending on.  Trustpower Limited and its subsidiaries (collectively, Trustpower) accepts no responsibility for any such virus or any effects of a virus on your systems or data.  Trustpower does not endorse anything in this email that is not related to its official business.

Please think of the environment before printing this email.

Users mailing list
Users at<mailto:Users at>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Users mailing list