There are many ways to do this depending on your needs. One of the simplest ways, for an ad-hoc query that probably for one time use it to use the PI SDK advanced search. You can find this search dialog in PI Processbook.

I don't think so. The old search was pretty nice; however, with each release it seems the tag search functionality of DataLink is improving. I am surprised the DataLink search isn't a common dialog. If you need it in a list, and don't have PI SQL tools (data access can be very pricey), you could use PI SMT current values to export save to a CSV and open in Datalink.

Of course, if you don't have many tags, you could use PI Builder (or old school PI-SMT Excel add-in) and just filter the results.

You could even search the PI server's message log for the "pibasess" subsystem and a message string like "point created", but that only goes back (by default) 35 days. I think Lal's or Dan's methods are better, but there are definitely many ways to do this.

Yeah, I agree. The WhereClause is limited for this use case. And for slow connections and/or large tag counts, client-side filtering could run into some trouble. Finally, is it really worth using PowerShell here if you want to consume the data elsewhere? Depending on your comfort-level, probably not.

But for a quick check on a small-moderately sized system, PowerShell could do the trick.

So two things. First, are you certain that there are tags that will match this criteria (created after 19-Mar-2018)? Second, your code snippet doesn't show how you would create any output - the second line would merely populate the $tags variable with the matching PIPoint objects. You would need additional code to output the results in some format: