When a worksheet contains a cell with longer text, which is right aligned and this text happens to be in the last column of the page, the worksheet is incorrectly split into pages and the last column gets transferred on the next page.
Workaround: Set explicitly the print area you would like to print.
worksheet.WorksheetPageSetup.PrintArea.SetPrintArea(new CellRange(0, 0, 38, 14));
LayoutHelper is not calculating Height properly in net standard.
Workaround: use SpreadFixedTextMeasurer
Provide the following options for the image:
When a file uses shared formulas, if the cell references are not explicitly written in the cell element, the formulas will not be shown correctly. This will manifest like a file that has a succession of slightly differing formulas in Excel and in RadSpreadsheet or RadSpreadProcessing they will be a succession of the same formula instead.
When autofit is applied on a button with a filter, the button width is not taken into account and it overlaps the text.
Expected:
Actual:
SpreadProcessing: InvalidOperationException when opening an XLS document with a named range that refers to a formula. The message is "Only applicable to named ranges". Opened correctly in Excel.
Parsing a document that contains a cell with wrapped multiline text and its row doesn't define a value for height, results in wrong row height when rendering or exporting to PDF.
Workaround: Fit the height of the row when it contains wrapped cells:
Worksheet worksheet = workbook.ActiveWorksheet;
CellRange wrappedCells = worksheet.GetUsedCellRange(CellPropertyDefinitions.IsWrappedProperty);
for (int i = wrappedCells.FromIndex.RowIndex; i < wrappedCells.ToIndex.RowIndex; i++)
{
worksheet.Rows[i].AutoFitHeight();
}
SpreadProcessing: Upon export, sheet reference in formulas such as VLOOKUP is lost when using whole row/column references.
For example the formula
=VLOOKUP("test",Sheet1!A:C,1,0) is exported as
=VLOOKUP("test",A:C,1,0)