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
Apparently there is a limit to the amount of values, resulting in some values never appearing. Search function only iterates over the limited list, so there is no way to get the over flooding values.
To Reproduce
Steps to reproduce the behavior:
Create an extractor for a multi-select with a long list of values (I don't know the limit). In this case it is a relationship property connected to 425 entities.
Some values are not accessible, they appear in no particular order.
@txau During the discussion in the product call, it came out that this seems not to be a bug, as it does what was decided in previous discussions, see #6800.
We can handle this as an enhancement is needed.
Describe the bug
On this control:
Apparently there is a limit to the amount of values, resulting in some values never appearing. Search function only iterates over the limited list, so there is no way to get the over flooding values.
To Reproduce
Steps to reproduce the behavior:
Note. This could be happening for selects, multi-selects and relationship fields. A working example here: https://cejil-test.dev.uwazi.io/es/settings/metadata_extraction/suggestions/675b18c6f21e5730e448f6ea
The text was updated successfully, but these errors were encountered: