This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| b_i:undefined_with_multiple_references [2023/03/09 03:35] – removed - external edit (Unknown date) 127.0.0.1 | b_i:undefined_with_multiple_references [2023/05/10 01:31] (current) – sean |
|---|
| | {{tag>Known_Issues, Issue:References Issue:UNDEFINED}} |
| | <invisible> This is the template for INHERITED known issues pages - add a tag to Issue: to allow this to show on the tagged page</invisible> |
| | |
| | ==== Undefined With Multiple References ==== |
| | <grid> |
| | <col sm="1"><invisible> This is a spacer column</invisible></col> |
| | |
| | <col sm="5">===Problem/Limitation Description=== |
| | Checking for ''UNDEFINED'' value of a multiple reference attribute (see [[docs:2000_concepts:0200_basics:0400_reference_attributes|Reference Attributes]]) in queries does not work correctly. For example, the following will not work:<code aim>FIND Account WHERE Account.Transactions IS UNDEFINED </code> |
| | </col> |
| | |
| | <col sm="1"><invisible> This is a spacer column</invisible></col> |
| | |
| | <col sm="5">===Work Around=== |
| | Use ''EXISTS'' or ''COUNT'' expressions, for example<code aim>FIND Account WHERE COUNT Transaction WHERE (Transaction IN Account.Transactions) = 0 </code> |
| | |
| | </col> |
| | </grid> |
| | |
| |