Hi All,
I am fetching a database data for a range using two datetimepickers ( “start time” and “endtime”) via namedquery in a table component of Ignition designer , I have few columns in the database table. That is working fine.
named query with two parameters
binded this named query in table component.data
Now I have to add a new column “split” in my dashboard which will have a button for each valid row.
This split column was not in the database table, I added it into the table component in column as follows
given pathview as “split column view” (having a split button)
added a tranform in the table component data - query binding
but when I enable this “split” column and open client runtime database filter works on for twice and whole dashboard got freeze/stuck/hang.
if I launch the project it again, again filter works for two times and then everything got freeze/stuck/hang even “navigations” also get freeze.
There is no error or warning in the gateway diagnotics Logs.
My named query is simple and quick responsive took only 0.18s to execute.
These is nothing in “split column view” only a simple button which will open a popup screen on click.
If someone can guide, it will be a great help guys.
I think you need to clarify this statement. Are you clicking the split button, using the table's filtering, or something else when everything freezes up?
This “split“ column, I enables from table.data.colums section: with attribute(field, visible,render,viewpath).
For filter the database data in my table component I am using, Datetime pickers.
When I launch my project, I am able to modify the datetime picker only first two times (and it wokrs too) after adding “split” column in the table component and then My whole ignition dashboard get frozen/stuck then nothing work- whether I click on any button, navigation to other screen, or any other component.
I think you can skip the scripting to add the “split” column. Just add an empty column on your original query and configure it on the columns props. Hope it makes sense, that’s what I would do 
2 Likes
In addition to removing the transform script, don't have the DB cast the datetimes as strings, leave them as datetimes and let the table control display style. You can adjust how they are displayed in the column properties.
Are you asking to skip this table.data- Query Binding Transform Script?
My objective is to create a new column “split“- which will have a “ADD/SPLIT“ button in all the respective row data. So I took a “split button” in “split column view” and modify “split“ column.render as VIEW.
as you can see now how it appears in the split column of the table,
Hi,
Not sure if this is your issue but with the table component in particular we have noticed that if you have a lot rows and have the filter.results.enabled set to true. It breaks the web socket if its over the max web socket size set in the ignition.conf file.
Also, we noticed that when rendering a view in a table the performance is poor if you dont set virtualized. This setting doesn't render all the rows but only the rows visible.
removed string casting and managed from table.props.column settings. thanks for suggestion.
But I couldn’t find the alternative of removing tranform script. Please elaborate your point of view.
it is already virtualized enabled in my project.
Just add the column in the query:
SELECT ignition_testing.downtime_date,
ignition_testing.downtime_start,
ignition_testing.downtime_end,
ignition_testing.actual_downtime,
ignition_testing."Part#",
ignition_testing."Job Number",
ignition_testing."LOC",
"" AS split
3 Likes
Yes, I added the same.
and removed transform and used this: Got the Split column in the dashboard.
but issue is still the same: after two filter everything frozen.
Check your browser console when "frozen", and also look on the gateway webpage threads diagnostics. Take a thread dump while things are 'frozen'. If you don't know what to look for, upload it here.
when it is frozen this is performance and thread, I attached dumped threads too during frozen. Please guide.
frozen thread_dump.json (195.8 KB)
