Apologies, cut and paste error. That is what I meant - manufacturerPartNrs.manufacturerPartNr In all honesty i've tried all combinations.
I've also tried other filter options like:
with the same result - full list of devices.
As an array, manufacturerPartNrs is not filterable. Our apologies, as this isn't called out anywhere in the documentation (we'll address that). To address your use case, please try the following query using our InventoryDetails resource:
EDIT: Nevermind, we do in fact support filtering here. It's not a feature that often gets used (because we don't have many collections of primitives in filterable resources) so I'd totally forgotten about it . Our filtering page covers this in the "Filtering on collections of primitives" section.
So you can either use the above query, which I believe satisfies your use case, or use the following:
It isn't needed in this case, correct.
To get into the weeds a little bit, because the presentation that we do here (<manufacturerPartNrs><manuFacturerPartNr>) doesn't represent the actual structure of the data, it's just a cosmetic way for us to take the array of Strings and display and marshal them into XML. The actual filtering that needs to happen is against elements parameter of the array itself (hence, the filter parameter is manufacturerPartNr.elements). When we do dotted notation against other collections, what you see in the XML represents the actual structure of our data; for example, in the InventoryDetails query above, summary is a reference to a separate object, so using the dotted notation lets the filtering logic know that it needs to apply that filter to the other object, rather than to the root InventoryDetails object. I'm not sure if you wanted these details, but that's why there's this difference here.
My apologies for the confusion. Thank you for reaching out