You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While creating the new field "Iterator", we realised that the sequences have the same behaviour as this field when introducing a FieldValueList with more than one value.
We wanted to discuss whether it is ok for the sequences to act like that, or it will be better to remove that behavior from them.
After the discussion, we agreed to remove the behaviour from the sequences when the FieldValueList has more than one value.
The text was updated successfully, but these errors were encountered:
Discussed in #275
Originally posted by IsaUlloa July 12, 2022
Hi,
While creating the new field "Iterator", we realised that the sequences have the same behaviour as this field when introducing a FieldValueList with more than one value.
We wanted to discuss whether it is ok for the sequences to act like that, or it will be better to remove that behavior from them.
After the discussion, we agreed to remove the behaviour from the sequences when the FieldValueList has more than one value.
The text was updated successfully, but these errors were encountered: