Skip updates when adding custom fields | Voters

Skip updates when adding custom fields

Arnout van der Vorst

When adding a new custom field for a source system, the entire population will be regarded as updated, which is something that is not always wanted and may cause way too much unnecessary enforcement activity. I would like to suppress or disregard update events.

June 23, 2021

Twan Duvigneau

Bernard Moeskops

Is there any update on this? I have a few customers that with every field change, I have to sit out over 100k actions...

Twan Duvigneau

In addition to this request, having a selector on each target system for "updatable fields" would result is a huge savings of unnecessary update actions. In these "updatable fields" select the fields in the HelloID dataset that would result in an update action. For example when you select the department field and an update happened on the costcenter field there will not be an update triggered, because the target system does not use the costcenter field in any way.

Niek de Melker

If we can reject blocked actions, we can achieve the same. an update on all users usually puts the target systems in a blocked state, after which we can stop this update.

Niek de Melker

maybe we can give some extra attention to this request, starting almost 70000 actions just to add an extra field is ridiculous.

Erika Eling-Farr

When adding a new field it should be possible to say 'from this date, only for new users'

Rick Nieuweveen

In addition, I would like to be able to determine per target system for which an update should be performed and for which it can be ignored after a change in the mapping.