Are there limits on dot walking in sysparm_query in the Table API? Qualifying a dot walked sysparm_field returns not data.

[Jerry Flood]

Using Table API I can return dot walked fields many levels deep, pseudo code example.

sysparm_fields=ref1.name,ref1.ref2.name

sysparm_query=ref1.name=REF1NAME

returns

{
"ref1.ref2.name": "REF2NAME",
"ref1.name": "REF1NAME",
},

but seems I can only qualify one level deep. The following returns nothing

sysparm_query=ref1.ref2.name=REF2NAME

Am I missing something ?

Thanks

Jerry

[Jerry Flood]

When I execute via the background script qualifying on the 3rd level field returns

field name '' not found in table ''

I am guessing that the table definition is missing something. Will need to speak to our design team. 

[Jerry Flood]

When reviewing the relevant tables in the schema map, the 3rd level relationship is not reflected as a referenced table so, at this point I am guessing that sysparm_query names are validated against the schema, however, sysparm_fields are resolved upon data retrieval.