Hello everyone,
I wonder if there is a simple way to use a Deduplicator bot on an optional field. Indeed, I noticed when I apply the deduplicator on an optional field that the null value must be entered in the redis because all messages (except the first one) that do not contain the field are dropped. Is there a workaround please?
I could work around this problem by adding two Sieve bots at the exit of the precedent bot that would jump the Deduplicator bot if the message doesn't have the field, but I don't find that to be optimal. Thus, I am open to any proposal that could help me.
Regards, Guillaume GRANJON de LÉPINEY | ggranjon@excellium-services.bemailto:ggranjon@excellium-services.be | PGP Key ID: 0xE2FD5ED1https://pgp.circl.lu/pks/lookup?search=0xE2FD5ED1&fingerprint=on&op=index CERT-XLM Incident Handler @ excellium-services.comhttps://excellium-services.com/ CERT-XLM | cert@excellium-services.commailto:cert@excellium-services.com | PGP Key ID: 0xD74E5AC0http://pgp.circl.lu/pks/lookup?op=vindex&fingerprint=on&search=0x67B311E5D74E5AC0 Excellium Services Belgium N.V. | Orion Bldg, Belgicastraat 13, B-1930 Zaventem, Belgium Mobile: +32 4 71 98 57 65 Emergency: +352 262 039 64 708 | emergency@excellium-services.commailto:emergency@excellium-services.com | PGP Key ID: 0x42662EFEhttps://excellium-services.com/assets/EMERGENCY_PKEY.asc
This email is confidential and may contain legally privileged information. If you are not the intended recipient, you should not copy, distribute, disclose or use the information it contains, please e-mail the sender immediately and delete this message from your system. Note: e-mails are susceptible to corruption, interception and unauthorised amendment; we do not accept liability for any such changes, or for their consequences. You should be aware that we may monitor your e-mails and their content. Excellium Services SA.