Came across a use case, and I think this could be a useful feature. I’m trying to create a table that would display part data, and I wanted to give the operator the ability to scan a barcode to pull up those records in the table relevant to the part.
I can make it work using a Named query binding with those values, but having the filter value as a property could make it a bit easier and more flexible for other applications.
I might be misunderstanding what you’re saying.
You can pass parameters into a Named Query so you could filter results in the WHERE clause of the query. You can also call stored procedures by making query text “EXEC dbo.spQuery” (MSSQL syntax) and pass parameters into that if you want to have your query in a stored procedure.
I’d build you an example quickly but I seem to be having a SQL driver issue on my test system so it can’t connect to databases.
The named query would be the alternate work around.
Ideally, I would like to have a property on the table though that I can bind a string/value to in order to filter the table. It already has a filter box that you can type an input into, but there isn’t a spot where we can write a value to that box based on a script.
OH! I see what you’re saying. I also fixed my db connection issue. It wasn’t the driver. This is a new system and I hadn’t opened up TCP/IP on my db server yet (LOL).
I tried using that filter box in the 8.0 build and it just blew up. One of the devs posted that there was a known issue with that feature and they are working on it. It seems that filter box should be doing what you are looking for.
Yeah, the issue occurs when there is null data in the table.
The filter box gets me half way there, but for example, if I wanted to be able to scan a barcode to set that filter, I can’t use that filter box and have to switch to named queries currently since that filter isn’t a property.
This should all be fixed in the next nightly build. Filtering should no longer blow up with null values or special characters. Also, the shape of the filtering prop will be changed so that you can write back to the filter text, as well as obtain results. It will look like this:
There will be quite a few bug fixes and added features. I will be posting all of these changes here http://forum.inductiveautomation.com/t/feedback-new-perspective-table/ later today, or early tomorrow morning.