Icons on Editable Grid.

We have a business requirement where we have around 50 rows per batch size + N number of columns. N columns can be 1 till N number which is determined by the file they upload or the data they entry.
So each row has a value which is mapped to a column and we determine if its 1 or 0 based on a simple click. We hold these mappings in the database so each particular field is one entry in the database. By clicking the toggle in the Right grid we set the value to 1 or 0.

Problem #1 since we have huge amount of data depending on the columns every click take a lot of time. (I'm only saving that particular field to a cdt and saving in the process model).

Problem #2 I tried to leverage the load by placing a local variable with the icon documents but it didn't improve. 

Problem #3 we can't lower the batch size but due to business requirements they require to show at least 50 rows if you have 50 columns that makes 2500 icons.

 

Any suggestions are appreciated find an attached image so you get the idea. 

 

 

 

  Discussion posts and replies are publicly visible

Parents
  • This sounds like it may be difficult to achieve both high performance and the business requirements for 50+ rows and columns, if there is any flexibility in the requirements I'd recommend using paging to lower the size of your data set. That said, you mention in problem 1 that you are saving to a cdt in the process model, is that happening on every click? If so, you may be able to improve performance by saving locally in the interface and adding a Save button to persist the changes to the database. Have you reviewed the performance view in the interface designer to pinpoint the cause of your slowness? That could help in improving your performance.
Reply
  • This sounds like it may be difficult to achieve both high performance and the business requirements for 50+ rows and columns, if there is any flexibility in the requirements I'd recommend using paging to lower the size of your data set. That said, you mention in problem 1 that you are saving to a cdt in the process model, is that happening on every click? If so, you may be able to improve performance by saving locally in the interface and adding a Save button to persist the changes to the database. Have you reviewed the performance view in the interface designer to pinpoint the cause of your slowness? That could help in improving your performance.
Children