Skip to content

Conversation

@dsagal
Copy link
Member

@dsagal dsagal commented Dec 4, 2025

Context

  1. When looking up .RefCol or .RefListCol on an empty reference list, return and empty RecordSet. This allows e.g. Table.lookupRecords(...).RefCol.Name to be used even when lookupRecords() returns an empty set. This previously didn't work.
  2. When looking up .RefListCol on a reference list, return a merged RecordSet. This already worked when e.g. Table.lookupRecords(...).RefListCol was set as the value for a RefList column, but now Table.lookupRecords(...).RefListCol.Name is similarly allowed.
  3. Allow RefList to get set to a single compatible reference value, turning it into a list.

Related issues

Resolves #1987 and #1985, which include some of the scenarios being addressed.

Has this been tested?

  • 👍 yes, I added tests to the test suite
  • 💭 no, because this PR is a draft and still needs work
  • 🙅 no, because this is not relevant here
  • 🙋 no, because I need help

1. When looking up .RefCol or .RefListCol on an empty reference list, return
   and empty RecordSet. This allows e.g. Table.lookupRecords(...).RefCol.Name
   to be used even when lookupRecords() returns an empty set. This previously
   didn't work.
2. When looking up .RefListCol on a reference list, return a merged RecordSet.
   This already worked when e.g. Table.lookupRecords(...).RefListCol was set as
   the value for a RefList column, but now
   Table.lookupRecords(...).RefListCol.Name is also allowed.
3. Allow RefList to get set to a single compatible reference, turning it into a list.

Resolves #1987 and #1985.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

lookupRecords followed by reference returns empty list instead of recordSet

2 participants