Hi Pieter, this is something I’d use very frequently – in most of my admin sessions I start from a card view>Elements: element settings tend to be conceptually grouped by a view in most of my projects, e.g. I may have a specific Trend Template that is needed only for elements belonging to a specific delivery point, so I’d select every different encoder in a view and assign the desired trending or alarming criteria. It’s also in the view card that I can easily spot any sort of inconsistent settings where perhaps not all elements were updated to use the latest alarm or trend tremplate defined for a given project. Since this is not possible, I end up changing them one by one if they are 2 or 3… if they are more, I simply jot down the names before going to the “Protocol & Templates” section as advised by Matthias.

I do use also the other section, but there I have no possibility to easily select elements that are not consistent with each other within the same view – I need to know the names/numbers to use the filter available in the “Assign Template” pop-up window – so I tend to refer to Protocol & Templates mainly for other tasks (checks on the protocol versions in use, template groups and so on).