Objects like Tasks can have child objects like Tags. So simply referencing "Tags" in the query meant it was looking at the entire Tags child object for a value named "QA". But since Tags is an object with its own collection of attributes each with their own distinct values (like Name), it didn't know what to look at.
The trick is realizing whether you're looking at an object (ex: Tags, WorkProducts, Owners) or an attribute (ex: Notes, DisplayColor, FormattedID) and for that you do have to have a bit of understanding around the object model and how that data is structured
Original Message:
Sent: 05-01-2020 01:49 PM
From: Eric Christ
Subject: Query Counter: Issue or User Error?
User error indeed! Thank you, David, that did the trick. A quick follow-up question. How can I tell from the WSAPI that I needed to do Tags.Name? Please know that I'm not a developer, just a humble and lowly business analyst.
Original Message:
Sent: 05-01-2020 01:22 PM
From: David LeDeaux
Subject: Query Counter: Issue or User Error?
Hi Eric,
Try this:
(Tags.Name contains "QA")
Original Message:
Sent: 05-01-2020 12:15 PM
From: Eric Christ
Subject: Query Counter: Issue or User Error?
I'm using the query counter to see the number of tasks that have a certain tag, such as QA. Per the WSAPI, I think I've got the right query but it's giving me an error that suggests it's not the right query. See screen shots below. Any suggestions?