I have a grid with 8000 rows, but I'm rendering only the first 1000, and by scrolling I'm rendering the rest.
I know the default of exportDataAsExcel is to export only the rendered rows,
Is it possible to export all the 8000 rows without rendering them?
Related
I would like to know if it is possible to have a sheet in Google Sheets with like 35 rows and have a table with much more rows of data with a scroll in it.
You can use a Table Chart.
Insert Chart
Select Table for the chart type
Set data range (for the one below B120:B300,C120:C300,E120:E300,F120:F300)
You'll have to have the data on a sheet somewhere and add each column separately as a data range. However it seems poorly supported. Last I checked it doesn't work very well on mobile. Also you can't format colors or font. It does allow sorting by column and alternating row color.
There is no way of doing exactly that. A good alternative is to freeze the rows that you always would like to see. This makes the scrolling not apply to them.
I have a need to print a large table across multiple pages which contains both header rows and a “header" column. Representative of what I would like to achieve is:
https://github.com/EricG-Personal/table_print/blob/master/table.png
I do not want the contents of any cell to be clipped, split between pages, or auto-scaled to be smaller. Each page should have the appropriate header rows and each page should have the appropriate header column (the ID column).
The only aspect not depicted is that some of the cells would contain image data.
Can I achieve this with jsPDF-AutoTable?
I'm adding 300 rows to a table dynamically and it's taking about 1.75 seconds to add the rows and at least another 1 to 1.5 seconds to render. I know this might sound like I am being picky but overall it's a 3+ second delay to show the table when this happens and the calcs behind that table execute really quickly.
I'm using a simple TableRowElement row = tBody.addRow();
and then row.addCell() for about ten columns of data. The data is coming from a List of Map objects.
If this is normal, then is there a way I can get the rows to render as they are created to sort of "speed up" the process from the user's point of view?
Thanks!
I am using Delphi XE5 and FireDAC.
I have a calculated field (Price_Each) and an aggregate field (Total_Price) in a dataset. The aggregate field sums the values of the Calculated Field (Price_Each).
The Dataset is displayed in a Dbgrid, and as there are many rows, some rows of the dataset are outside the Grid view window and need to be scrolled into view.
The issue I am having is that the Aggregate (sum) I get is only for those value of the Price_Each that are displayed in Rows in the DBgrid that are shown. So that Sum is incorrect. When I Scroll the DBGrid to bring the other rows into the View, then the Sum is Updated and then correct.
I want the Sum to be calculated for all rows in the Dataset and not just those rows visible in the DGrid?
The reason why I am using Calculated Fields is that there is some further Logic that I use to calculate the price and I would not be able to do this in an SQL statement that fetches the data.
I there any way to do this?
NOTE: I have already tried setting FetchOptions to fmAll and it did not work. Still I have to scroll the Grid ?
Is it possible to change the behaviour of tableview row culling?
For instance, change it so that it doesn't remove/destroy cells unless they are at least 4 rows off screen (in either direction) ?
So to visualize this:
-- Row 1
-- Row 2
-- Row 3
-- Table view visible top here. Any rows above are off screen
-- Row 4
-- Row 5
So in this scenario, imagine that the default behaviour is to cull/destroy rows as soon as they leave the visible screen area. So in this case, row's 1>3 would be destroyed and recreated as they come back onto the screen.
This can result in some visual hiccups, depending on how you are gathering data and how much is being displayed in the cells etc.
So to make the row recreation less obvious on the eye, i would like to higher the limit, to only cull rows after they move up either x amount of rows above the table view top, or after a row is y amount of pixels above (i.e not visible) the cut off point.