This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| ref:b_i:use_of_in_with_complex_identifiers [2026/08/13 00:42] – removed - external edit (Unknown date) 127.0.0.1 | ref:b_i:use_of_in_with_complex_identifiers [2026/08/13 07:11] (current) – external edit 127.0.0.1 |
|---|
| | {{tag>Known_Issues, Issue:IN, Issue:Query}} |
| | <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> |
| | |
| | ==== Use Of IN With Complex Identifiers ==== |
| | <row> |
| | <col size="1"><invisible> This is a spacer column</invisible></col> |
| | |
| | <col size="5">===Problem/Limitation Description=== |
| | ''IN'' expressions using complex identifier of the reference list are not supported if used in subqueries. For example, the following query is not supported:<code aim>FIND Client WHERE (COUNT Account WHERE (Account IN Client.Carrier.Accounts) > 3) </code>Note that the following query is supported:<code aim>FIND Client WHERE (COUNT Account WHERE (Account IN Client.Accounts)>3) </code> |
| | |
| | </col> |
| | |
| | <col size="1"><invisible> This is a spacer column</invisible></col> |
| | |
| | <col size="5">===Work Around=== |
| | Avoid using such constructs in queries |
| | </col> |
| | </row> |
| | |
| |