Getting Handsontable to work with QuickBase
I just downloaded the trials for Handsontable to determine the use vs. cost within our QB apps. Does anyone have experience getting it installed that they would be willing to help me with? I am fami...
Forum Discussion
In reality, all our company needs from Handsontable is filtering like Excel. The rest is of no real value, but may come in handy. Yes we have to move on from Excel, but QB is seriously lacking in its filtering ability. Sorting a column is fine, but we need to be able to filter data in anyway way we want-quickly.
We can build several "standard" dynamic filters that will accomplish filtering our projects in ways that we need on a continuing basis. The issue lies in the fact that often we need to find a number of projects, via a project number, that is a one-off situation. Our data is like everyone else's data, projects and the associated information, but we get requests from our client for a set of projects that match a specific criteria, and this is a one off.
In Excel, we can go to a column and type in project numbers (as a grouping) and get back results for that number of projects. We may also need to know which projects are located at a certain place, or are in a certain order. Going in and creating a dynamic filter for each of these one-offs is very time consuming. What we can do with 2-4 clicks in Excel's filtering takes more typing and time in QB to accomplish.
QB is a very good platform, but there are reasons that people continue to use spreadsheets, like Excel. The filtering of data is much faster and there are no limits to the number of data points when making a plot. I have been working with IOL and calling D3 so the plotting part is getting easier to understand.
I asked Handsontable if they would just provide the filtering part of their code since it is exactly what we need. They said "Nope". It may turn out that we come to CirrusOps to get this 1 thing implemented, but until my group makes a decision to move forward finally with the transition to QB, I am still just playing and learning how to use the software.
Thanks to you, Matthew, and Dan for the help that y'all provide to me as I ask the very simple questions.
Cheers!
We can build several "standard" dynamic filters that will accomplish filtering our projects in ways that we need on a continuing basis. The issue lies in the fact that often we need to find a number of projects, via a project number, that is a one-off situation. Our data is like everyone else's data, projects and the associated information, but we get requests from our client for a set of projects that match a specific criteria, and this is a one off.
In Excel, we can go to a column and type in project numbers (as a grouping) and get back results for that number of projects. We may also need to know which projects are located at a certain place, or are in a certain order. Going in and creating a dynamic filter for each of these one-offs is very time consuming. What we can do with 2-4 clicks in Excel's filtering takes more typing and time in QB to accomplish.
QB is a very good platform, but there are reasons that people continue to use spreadsheets, like Excel. The filtering of data is much faster and there are no limits to the number of data points when making a plot. I have been working with IOL and calling D3 so the plotting part is getting easier to understand.
I asked Handsontable if they would just provide the filtering part of their code since it is exactly what we need. They said "Nope". It may turn out that we come to CirrusOps to get this 1 thing implemented, but until my group makes a decision to move forward finally with the transition to QB, I am still just playing and learning how to use the software.
Thanks to you, Matthew, and Dan for the help that y'all provide to me as I ask the very simple questions.
Cheers!