diff --git a/Document-Processing/Excel/Spreadsheet/React/images/image.png b/Document-Processing/Excel/Spreadsheet/React/images/image.png new file mode 100644 index 000000000..82fec6a26 Binary files /dev/null and b/Document-Processing/Excel/Spreadsheet/React/images/image.png differ diff --git a/Document-Processing/Excel/Spreadsheet/React/troubleshooting/http-413-entity-too-large.md b/Document-Processing/Excel/Spreadsheet/React/troubleshooting/http-413-entity-too-large.md new file mode 100644 index 000000000..da6b31471 --- /dev/null +++ b/Document-Processing/Excel/Spreadsheet/React/troubleshooting/http-413-entity-too-large.md @@ -0,0 +1,55 @@ +--- +layout: post +title: HTTP 413 "Entity too large" in React Spreadsheet control | Syncfusion +description: Resolve the HTTP 413 'Entity too large' error when exporting large Excel files from React Spreadsheet by increasing server request limits. +platform: document-processing +control: Spreadsheet +documentation: ug +--- + +# Troubleshoot HTTP 413 "Entity too large" error + +Sometimes, when exporting the Spreadsheet with a large dataset, an `Entity too large` issue may occur. This is related to an HTTP request attempting to receive a large amount of data. To resolve this, configure your server to handle larger data transfers. + +## Solutions + +To resolve this, configure your local Web API back-end to accept larger request bodies. Add the following settings to increase the allowed request size: + +### Step 1: Update web.config (Server-side) + +Add or update the `requestLimits` configuration in your WebAPI's `web.config` file to increase the maximum allowed content length: + +```xml + + + + + + + + + + +``` + +### Step 2: Update Program.cs (Server-side) + +Configure the Form Options in your `Program.cs` to handle larger form submissions: + +```csharp +builder.Services.Configure(options => +{ + options.ValueLengthLimit = int.MaxValue; // or set a custom larger value + options.KeyLengthLimit = int.MaxValue; + options.MultipartBodyLengthLimit = long.MaxValue; +}); +``` + +Additionally, we recommend setting the `isFullPost` property to `false` in the `beforeSave` event when exporting large Excel files. When `isFullPost` is `false`, to mitigate Spreadsheet can lead to performance issues such as timeouts or delays, particularly due to the size and complexity during export. See the `isFullPost` [documentation]((https://help.syncfusion.com/document-processing/excel/spreadsheet/react/performance-best-practices#handling-large-file-saves-with-isfullpost-option) ) for details. + +## See Also + +* [Performance Best Practices](../performance-best-practices) +* [Open excel files](../open-excel-files.md) +* [Save Excel files](../save-excel-files.md) +* [Web Service](../web-services/webservice-overview.md) diff --git a/Document-Processing/Excel/Spreadsheet/React/troubleshooting/spreadsheet-double-header.md b/Document-Processing/Excel/Spreadsheet/React/troubleshooting/spreadsheet-double-header.md new file mode 100644 index 000000000..47c951d0b --- /dev/null +++ b/Document-Processing/Excel/Spreadsheet/React/troubleshooting/spreadsheet-double-header.md @@ -0,0 +1,42 @@ +--- +layout: post +title: Fix double header issue in React Spreadsheet +description: Fix duplicate or misplaced header caused by multiple refresh/resize actions and redundant lifecycle calls. +platform: document-processing +control: Spreadsheet +documentation: ug +--- + +# Issue + +In some scenarios, the Spreadsheet header appears twice or is rendered below the data instead of at the top. The issue in the Spreadsheet component can occur when multiple refresh actions are triggered, such as calling `refresh()` action before a previous render or sheet refresh has completed. The below image show double header rendered issue in spreadsheet: + +![Double header example](../images/image.png) + +Cause: The double header can appear when a `refresh()` or `resize()` is triggered before a previous render or sheet refresh completes (for example, overlapping programmatic refreshes or visibility changes), causing the header to be rendered again in the wrong position. + +## Troubleshooting checklist (in order) + +Follow these steps in order to diagnose and fix the double-header issue: + +1. **Ensure only one refresh/resize at a time:** Ensure only one `refresh()` or `resize()` action is triggered at a tim before the previous render completes. + +2. **Avoid refresh in rapid UI updates:** Do not call `refresh()` inside rapid UI updates, tight loops, or multiple event handlers—debounce or throttle these calls where appropriate. + +3. **Use lifecycle events carefully:** Use lifecycle events (`created`, `dataBound`, etc.) without redundant `refresh()` or `resize()` calls. + +4. **Confirm package version:** Confirm the Spreadsheet package version you are using latest version. + + +5. **Initialization & mounts:** Ensure the Spreadsheet component is initialized only once and that no duplicate mounts occur in your application. + +6. **Frozen panes / merged cells:** Verify frozen panes, hidden rows, or merged cells that could affect header rendering or position. + +7. **CSS/layout inspection:** Inspect CSS/layout (positioning, `z-index`, transforms) that may visually duplicate or misplace the header. + + +## See Also + +* [Performance Best Practices](../performance-best-practices) +* [Resize handling](../mobile-responsiveness) +* [Freeze panes](../freeze-pane)