Completed
Last Updated: 13 Nov 2024 08:50 by ADMIN
Release 2024.4.1106 (Q4 2024)
Hi, I have a spreadstreamprocessing project, in which I read excel files to import data into my database based on some criteria. I copied code from sample and made changes, but I am facing a problem in reading whole file. If there is a cell with Error, rowImporter stops working after it.  It does not throw any exception or error, just ends reading further from sheet. Is there any way to ignore cells with ERROR and read remaining cells?
Completed
Last Updated: 15 May 2024 06:28 by ADMIN
Release 2024.2.426 (2024 Q2)

If  row has a property set on it (for example "hidden" or a style), but it does not otherwise have any cells in it, the application might run into an infinite loop. The xml will look like this:

	<sheetData>
		<row r="1" spans="1:2" x14ac:dyDescent="0.35">
			<c r="A1"><v>1</v></c>
			<c r="B1"><v>2</v></c>
		</row>
		<row r="2" spans="1:2" s="1" customFormat="1" x14ac:dyDescent="0.35"/>
	</sheetData>

The last row has formatting applied, so it is present as an element, but has no cells. This file (when the xml is not formatted) will cause an infinite loop on import.

Completed
Last Updated: 13 Nov 2024 08:50 by ADMIN
Release 2024.4.1106 (Q4 2024)
Add support for importing files with absolute relationship target paths.
Completed
Last Updated: 19 Jan 2023 14:56 by ADMIN
Release R1 2023
When creating a SpreadPatternFill instance with SpreadPatternType 'Solid', the PatternColor and BackgroundColor properties have swapped values. The cells with the applied fill have a background with the color of the BackgorundColor property instead of the color of PatternColor.

Workaround: Swap values when setting the properties.
Completed
Last Updated: 14 Feb 2023 11:20 by ADMIN
Release R1 2023 SP1
Provide API that allows retrieving of the cached formula value
Completed
Last Updated: 27 Feb 2023 11:24 by ADMIN
Release R1 2023 SP1
Rows import stops after reading a formula cell.
Completed
Last Updated: 19 Jan 2023 14:56 by ADMIN
Release R1 2023
While reading the content, the ReadCellValue method throws NotSupportedException: "The RichText value type is not supported". Although the rich text in the cells is not supported, the library could parse the text content and avoid throwing errors.
Completed
Last Updated: 19 Jan 2023 14:56 by ADMIN
Release R3 2022 SP1
When importing a document containing more than one Number Formats (numFmts) with the same format code (formatCode) an exception is thrown: System.InvalidOperationException: 'Same item with different index exists.'

Completed
Last Updated: 10 Nov 2022 06:29 by ADMIN
Release R3 2021 SP1
Exception when exporting a conational formatting rule with no formatting 
Completed
Last Updated: 01 Nov 2021 07:46 by ADMIN
Release R3 2021 SP1
Created by: Joon-Sae
Comments: 1
Category: SpreadStreamProcessing
Type: Bug Report
1
Exception when color does have a complete value.
Completed
Last Updated: 06 Jul 2023 08:12 by ADMIN
Release R3 2021
Created by: Gil
Comments: 3
Category: SpreadStreamProcessing
Type: Feature Request
0
Some of the required properties are Orientation and Page size.
Completed
Last Updated: 26 Jul 2021 07:24 by ADMIN
Release R3 2021
When using the API for measuring the cell content size the results are not correct.
Completed
Last Updated: 17 Mar 2021 09:11 by ADMIN
Release R2 2021

When calling SpreadExporter.CreateWorkbookExporter method and referencing Trial assemblies an exception is thrown: System.ArgumentException: 'An item with the same key has already been added.'

This behavior is observed both with the NuGet packages and DLLs.

It is not observed with Trial DLLs version 2020.3.1019

Completed
Last Updated: 16 Mar 2021 13:25 by ADMIN
Release R2 2021
Created by: Dan
Comments: 1
Category: SpreadStreamProcessing
Type: Feature Request
1
The space="preserve" attribute defines that the visualizing application must show all the spaces inside a string value. Without this attribute, MS Excel trims the blank spaces of the values.
Completed
Last Updated: 13 Dec 2018 15:23 by ADMIN
ArgumentException with clarification similar to  "'\u001f', hexadecimal value 0x1F, is an invalid character." is thrown when trying to export document containing characters which are not supported in XML document - such as some control characters like 0x00, 0x1F, 0x1B, etc. Such characters are described in the XML specification here: https://www.w3.org/TR/xml/#charsets.
Although the escaped strings are not supported (see related 181318), the library could prevent the exception and export the document successfully by skipping such characters.
Workaround: remove such characters before the export. Check the following StackOverflow answer for some ideas on code for replacing the characters: http://stackoverflow.com/a/14323524/259206


Completed
Last Updated: 27 Nov 2018 11:29 by ADMIN
At this point, CsvWorkbookExporter flushes the data to the underlying stream each time a new data is added. This leads to decreased performance. Ensure the best possible performance by flushing the stream at the end of the content generation.

Completed
Last Updated: 19 Sep 2022 13:17 by ADMIN
Release R3 2022
ADMIN
Created by: Anna
Comments: 2
Category: SpreadStreamProcessing
Type: Feature Request
42
In addition to the fast document generation, the SpreadStreamProcessing can be adapted to import documents significantly faster than SpreadProcessing.
Completed
Last Updated: 17 May 2021 08:29 by ADMIN
Release R2 2021
Provide a way to measure text on different platforms so the user can pass the cell value and SpreadCellFormat and get the size of the text in pixels. This way we will be able to implement auto-fit to width functionality (AutoFitWidth), at least for the .NET Framework implementation. It will be able to measure the width of all cells in a column and set the value as column width in pixels.
Completed
Last Updated: 21 Jul 2017 11:19 by Robert Madrian
ADMIN
Created by: Peshito
Comments: 3
Category: SpreadStreamProcessing
Type: Feature Request
1
The UTF8 with BOM encoding should be used to properly preserve the different characters.

Available in R3 2017 Official Release.
Completed
Last Updated: 30 Mar 2017 14:21 by ADMIN
When a cell value contains commas or new lines, they are not escaped on export to CSV and single value is exported as multiple values.

Workaround: Escape the value manually. For example, use the following extension method to set string cell values:
internal static class CellExporterExtensions
{
    public static void SetValue(this ICellExporter cell, string value, SpreadDocumentFormat format)
    {
        if (format == SpreadDocumentFormat.Csv)
        {
            if (value.Contains(","))
            {
                // escape all quotes with double quotes
                value = value.Replace("\"", "\"\"");

            }

            // enclose all values within quotes
            value = string.Format("\"{0}\"", value);
        }

        cell.SetValue(value);
    }
}

Available in LIB version: 2017.1.403
1 2