While struggling with a strange multi-valued direct flow rule today I discovered something I did not know before 🙂
I kept on getting a “mv-constraint-violation” error, but only on certain of the multi-valued attribute flows.
Doing by research I found two rules that apply here:
- All members within the multi-valued attribute have to be unique
- Each element must be less than 900 bytes
Looking at the data I confirmed that neither of these rules applied. After a lot of different dead-ends, I found the error.
In the original deployment the Metaverse destination attribute was created as a “Indexed-String”. Trying out a hunch I changed all flows to a newly created “String (non-indexed)”.