OfficeIMO.Excel.OpenDocument 3.4.4

OfficeIMO.Excel.OpenDocument

OfficeIMO.Excel.OpenDocument explicitly converts between OfficeIMO.Excel workbooks and native OfficeIMO.OpenDocument spreadsheets. It does not invoke Excel or LibreOffice; the adapter depends on the two OfficeIMO object-model packages it connects.

using OfficeIMO.Excel;
using OfficeIMO.Excel.OpenDocument;
using OfficeIMO.OpenDocument;

using ExcelDocument workbook = ExcelDocument.Load("report.xlsx");
OdfConversionResult<OdsDocument> conversion = workbook.ToOpenDocumentResult();
conversion.Value.Save("report.ods");

foreach (var mapping in conversion.Report.Mappings) {
    Console.WriteLine($"{mapping.Feature}: {mapping.Status} ({mapping.Count})");
}

The adapter maps worksheets, typed cell values, formulas, hyperlinks, comments and ODF annotations, merges, row/column layout, named ranges, number-format categories, and a basic style subset. Basic cell styles include left/center/right/justified horizontal alignment, top/center/bottom vertical alignment, and text wrapping in both directions. ODS cell, row, column, and family-default styles follow ODF precedence for populated cells. Blank cells styled only through row, column, or family defaults are omitted with explicit loss. Value-dependent alignment, direction-sensitive alignment, alignment across a selection, indentation, and shrink-to-fit remain explicit conversion loss. Borders are outside the mapped subset. List, whole-number, decimal, text-length, constant-date (1904–9956), and whole-second time validations round-trip with input/error messages and error severity. Excel date and time bounds may use numeric serials or simple DATE(year,month,day) and TIME(hour,minute,second) formulas with literal, in-range arguments. Custom validation formulas round-trip when one contiguous range uses a local cell comparison against a number, text literal, or another local cell, or ISBLANK, ISNUMBER, or ISTEXT on one local cell. These predicates can be combined with AND, OR, and unary NOT. The ODF rule records the range's first cell as its formula base. Unsupported ODS validation expressions remain editable as ODF conditions and are reported during conversion. Unsupported Excel rules, including dynamic date formulas, subsecond times, other custom-formula functions, multiple target ranges, and dates outside the guaranteed OpenFormula range, are omitted with an explicit loss report.

The ODS-to-Excel route maps up to 16 ordered numeric cell-content() comparisons or cell-content-is-between / cell-content-is-not-between conditions with literal numeric bounds on one cell style to Excel cell-value rules. Rule priority and stop-if-true preserve the first matching style. Each applied common table-cell style needs a direct background fill or supported font property. The Excel differential style receives direct text color, explicit bold/italic/underline/strikethrough on or off, one font family, and absolute font sizes from 1 to 409 points. Font-only rules do not need a fill. Range bounds must be in ascending order. Double or patterned line-through styles are not mapped.

The route covers up to 4,096 styled cells per source style on each sheet when basic styles are included. The report marks mapped rules as approximate because other ODF applied-style properties, font-family fallback lists, relative font sizes, and evaluation details are not transferred. A style with more than 16 maps or any unsupported map remains wholly unsupported. Formula bounds, other conditions, maps without a supported direct style property, and rules above the cell limit remain unsupported.

The Excel-to-ODS route maps up to 16 numeric cell-value rules with direct-RGB solid differential fills and exactly representable plain decimal bounds. Rules may share a contiguous range or use separate, nonoverlapping ranges in one sheet. It preserves priority and first-match behavior within each range when every rule except the last uses stop-if-true, and applies the maps to at most 4,096 cells in total that have no basic cell style. The report marks these mappings as approximate because Excel differential formatting and ODF applied styles have different evaluation models. Styled target cells, overlapping ranges or merges, theme or indexed fills, exponent or higher-precision bounds, mixed differential styles, noncontiguous range references, other conditions, and rules beyond the limits remain explicit conversion loss; an unsupported group leaves the sheet's conditional chain unmapped.

The ODS-to-Excel route also maps embedded, nonstacked column, bar, and line charts with up to 16 series and 4,096 numeric points per series. It retains category labels, series names and values, the title, and approximate size and cell placement. The Excel chart receives copied values rather than a live link to the source ODS cells; chart styling, axes, and legend settings are not transferred, so each mapped chart is reported as an approximation. Unsupported or unsafe chart objects remain explicit conversion loss.

The Excel-to-ODS route maps worksheet-linked column, bar, and line charts with up to 16 series and 4,096 numeric points per series. The ODS chart links to converted source cells and retains category labels, series names, title, and approximate placement. Styling, axes, legends, and interactions are not transferred, so each mapped chart is reported as an approximation. Pivot charts, other chart types, clipped source ranges, and charts outside the conversion limits remain explicit loss.

Worksheet-source pivot tables also have a bounded two-way route. One pivot with row and/or column fields and one standard aggregate field can become an ODS data pilot, then return as an Excel pivot when its source and output are on the same sheet. The conversion report marks mapped pivots as approximate: source caches, styling, sorting, subtotals, layout details, and filter-button presentation are not transferred. Page filters, hidden or selected members, grouping, calculated fields, multiple data fields, cross-sheet sources, and source cells clipped by conversion limits remain explicit loss. ODS output cells are copied as ordinary cells; OfficeIMO does not evaluate a pivot during conversion.

For Excel-to-ODS pivot conversion, row and column grand totals must remain enabled. ODS-to-Excel conversion accepts only implicit/default totals; explicit ODF grand-total elements remain unsupported. In both directions, at least one axis field is required and at most 16 distinct row/column fields are supported. The source needs unique, nonempty headers that exactly match its field bindings, one supported standard aggregate, and no Values-axis field. The generated two-row Excel pivot footprint must fit within the declared ODS target range and cannot overlap any retained local pivot source, including sources of unsupported or later pivots, or an earlier generated output or retained merge. Excel-to-ODS also excludes pivot output ranges intersecting worksheet merges. Both ranges must retain their source cells, and performed source and target retained-range scans share a one-million-cell area budget per conversion. Range membership and collision planning also share bounded work budgets; if those budgets are exhausted, remaining affected pivots are reported as unsupported. Pivot names must be nonempty, already trimmed, and distinct without regard to case. Other pivots are reported as unsupported.

ODF permits one annotation per spreadsheet cell. An Excel threaded discussion is therefore flattened into one readable annotation transcript per cell, retaining available author, timestamp, identity, parent, resolved-state, and body metadata while reporting the thread mapping as an approximation.

Formula and address conversion uses typed Excel A1/OpenFormula syntax. Quoted worksheet names, absolute references, ranges, arrays, unions, intersections, strings, and separator changes are handled structurally; unsupported structured or external references fail closed and retain cached ODS values where available.

ExcelOpenDocumentConversionOptions bounds rows, columns, converted cells, and merge or validation-range materialization in both directions. Content omitted by those limits or disabled style options is returned as a Skipped mapping rather than silently disappearing. Set LossPolicy = OdfConversionLossPolicy.ThrowOnAnyLoss when a workflow must reject any approximation, skipped feature, or unsupported mapping.

Dependency footprint

• External: None.
• OfficeIMO: OfficeIMO.Excel and OfficeIMO.OpenDocument; the adapter owns bounded feature mapping and fidelity reports.

See the complete OfficeIMO package map for related formats and conversion paths.

Generated capability summary

This table is generated from the package-neutral OfficeIMO operation catalog. The detailed source contracts remain authoritative for feature-level behavior and limitations.

The complete rows for OfficeIMO.Excel.OpenDocument are published in the generated operation contract.