Limitations to dropdown reference selector?

Are their limitations to the content of a drop down reference selector? Normally we use select forms with large amount of possible reference values but for quick testing purposes we use forms with dropdown ref.selectors in stead of select forms and we noticed that their is a limitation to the number of records in a dropdown ref,selector. Worse, when an existing reference has a value that is in de non-visible range of the dropdown the value is shown as blank. After commit the value is gone and not-null constraint are triggered (value is not visible/reselectable). Looks like a bug! or is this a known limitation?
2 answers

The content of a drop down reference selector is indeed limited to 1000 items. That is because Internet Explorer freezes or even crashes when adding a large number of items to a drop down. You should see an exception when the number of items exceeds the maximum of 1000 items. (It might be a better idea to replace a drop down with a select form when this happens, because you can not always predict how many items will be shown.)

The reference selector should not clear its value if the selected value is not in the set due to this limitation, so this is indeed a bug. Could you file a ticket for this?


I believe there is a maximum number on the results shown in a dropdown menu of 250.

The other behavior, where a saved reference does not show up if it does not match the constraint is not something I would call a bug: if the object you are referencing does not show up due to a constraint, this is the behavior I would expect. Sometimes, it is annoying though, but I use the following work arounds:

  • If I use an XPath constraint, I use[ XPathConstraint or Relation = '[%CurrentObject%]']
  • If I use a data source microflow, I retrieve the entity that is currently used and add it to the result set.