Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

I can't say for certain, but there seems to be some sort of limit on the number of items that can be in a value list.

Say I have a list which is based upon a field:

[car parts::serialNo]

And then I use

[color:red]ValueListItems ( fileName; valuelist )

There will sometimes be items missing.

If instead I use

[color:red]List ( car parts::serialNo )

This problem does not occur. (Before anyone asks, the reason for not using list in the first place is for backwards-compatibility).

Has anyone seen anything similar? Is there a known limit on value list items?

I am not sure what you mean by missing. A value list shows only unique items, and this is reflected in the result of ValueListItems() too, while the result of List() will include duplicates.

  • Author

By missing, I mean if you do a PatternCount(Query)>0 on both datasets it will sometimes evaluate as false on the ValueList type, but true on the List type.

Hope that makes sense

That could easily happen if the value list is defined to show only a second field, or to sort by a second field. Again, items with duplicate values in the second field would be removed from the list. If that's not the case, post a file showing the problem.

EDIT:

Another possible cause is values longer than the index limit (110 characters, IIRC). Values that are identical up to the limit are considered duplicates.

Edited by Guest

It could also have to do with the context in which List() is run.

ValueListItems() pulls each unique value from the entire index, List() grabs all the values from the set of records related to the current record.

Edited by Guest

  • Author

That could easily happen if the value list is defined to show only a second field, or to sort by a second field. Again, items with duplicate values in the second field would be removed from the list. If that's not the case, post a file showing the problem.

Neither of those things are the case here. Unfortunately I cannot post the file for IP reasons. I will try to find a way to replicate the problem in a clean file.

Another possible cause is values longer than the index limit (110 characters, IIRC). Values that are identical up to the limit are considered duplicates.

This sounds plausible. I will check what the average length of the values is.

  • Author

Hmm.

Well in the process of creating a clean file, I've been completely unable to replicate the problem thus far.

The only oddity I could find was that the indexing on the field used in the value list was set to "minimal" which I suspect might account for the problem somehow.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.