I am trying to create a dashboard to show the results of tests on a master gauge, and I want the operator to be able to enter the results into a popup that I have made. The popup saves the values into a set of memory tags. Then I want the operator to be able to press a button to add a row to a powertable or regular table, and have the data charted on a line graph.
My question is, how do I get the table to update from the memory tags? I know there is a way to do it, and I am just overlooking it.
I am using the memory tags because my company has access to databases looked down tighter than a drum, and I am trying to avoid having to go through the red tape to get a new database, or a table made within the database.
Where is the table getting its original set of data from, a DB table? Or will the table data be filled entirely from operator entry? Does the data need to persist between sessions?
This sounds like a typical use case for a DB table to hold all past entries. The button would insert a new row into the DB table and then trigger the display table on the vision client to re-poll the DB table.
If you are set on not using a DB table ( I do not recommend this approach):
If it only needs to persist for a single session, a client dataset memory tag can be directly bound to the table, add a row to the dataset to update the table.
If it needs to persist across multiple sessions, then use a Gateway Dataset memory tag. Add a row to the dataset to add a row to the display table. This opens you up to race conditions if multiple operators are entering data in the same time frame.
The Initial table would be created by me. Then subsequent tests, (they are only done once a month,) would be entered into a popup by the operator.
I am only exploring the no database option as it is nearly impossible to get our company to give authorization for DB access to more than a couple people. (Their mistake in my opinion, but nothing I can do.) I am still trying to get the access. So this is more of a last ditch effort if I can't.
It would need to be a single instance, but the data would need to be kept long term.
I think I will just keep working on pushing to get the DB access I need, and tell them we can't properly implement this without it.
DB is the only viable solution. I would tell your bosses that you cannot proceed without a database table. You are otherwise wasting your time and risking loss of your long-term data.