We're using Telerik.ReportViewer.WebForms.ReportViewer for exporting to another files format but only exported to excel file I got error message below. please help to advise for this error. Server Error in '/' Application. Attempting to get range {22,19}{10,3},Merged=False,Parent=printPackingList2[0], that intersects with an already merged range. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Attempting to get range {22,19}{10,3},Merged=False,Parent=printPackingList2[0], that intersects with an already merged range. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [InvalidOperationException: Attempting to get range {22,19}{10,3},Merged=False,Parent=printPackingList2[0], that intersects with an already merged range.] Telerik.Reporting.Excel97.Worksheet.GetRange(Int32 col, Int32 row, Int32 colSpan, Int32 rowSpan) +186 Telerik.Reporting.ExcelRendering.Excel97.Worksheet.Telerik.Reporting.ExcelRendering.IWorksheet.GetRange(Int32 col, Int32 row, Int32 colSpan, Int32 rowSpan) +73 Telerik.Reporting.ExcelRendering.RenderingItem.GetRange(IWorksheet worksheet, TableLayoutInfo layoutInfo) +381 Telerik.Reporting.ExcelRendering.RenderingItem.Render(IWorksheet worksheet, TableLayoutInfo layoutInfo) +78 Telerik.Reporting.ExcelRendering.RenderingItemContainer.RenderInternal(IWorksheet worksheet, TableLayoutInfo layoutInfo) +141 Telerik.Reporting.ExcelRendering.Section.RenderInternal(IWorksheet worksheet, TableLayoutInfo layoutInfo) +62 Telerik.Reporting.ExcelRendering.RenderingItem.Render(IWorksheet worksheet, TableLayoutInfo layoutInfo) +638 Telerik.Reporting.ExcelRendering.RenderingItemContainer.RenderInternal(IWorksheet worksheet, TableLayoutInfo layoutInfo) +141 Telerik.Reporting.ExcelRendering.Report.RenderInternal(IWorksheet worksheet, TableLayoutInfo layoutInfo) +786 Telerik.Reporting.ExcelRendering.RenderingItem.Render(IWorksheet worksheet, TableLayoutInfo layoutInfo) +638 Telerik.Reporting.ExcelRendering.Report.Render(IWorkbook workbook) +373 Telerik.Reporting.ExcelRendering.Excel97.ExcelReport.Telerik.Reporting.Processing.IRenderingExtension.Render(Report report, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback) +184 Telerik.Reporting.Processing.ReportProcessor.RenderCore(ExtensionInfo extensionInfo, IList`1 reports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback) +1386 Telerik.Reporting.Processing.ReportProcessor.RenderCore(String format, IList`1 reports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback) +103 Telerik.ReportViewer.WebForms.ReportExportOperation.RenderReport(String format, IList`1 processingReports, Hashtable deviceInfo, IRenderingContext renderingContext) +259 Telerik.ReportViewer.WebForms.ReportRenderOperation.PerformOperationOverride() +340 Telerik.ReportViewer.WebForms.HandlerOperation.PerformOperation(HttpContext context, ICacheManager cacheManager) +74 Telerik.ReportViewer.WebForms.BasicHandler.ProcessRequest(HttpContext context) +276 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +341 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69
When selecting a table element in the content area via the Dom inspector, Delete Table does not remove the table. You can use the RemoveElement from DOM inspector as a temporary workaround.
Currently, opening the CustomColorPallete popup always selects the #808080 color.
To have this behavior use the custom code solution below:
<telerik:RadColorPicker runat="server" ID="RCP" EnableCustomColor="true" OnClientLoad="OnClientLoad" />
<script>
function OnClientLoad(sender, args) {
$telerik.$(sender._customColorButton).click(refreshPalette(sender));
}
function refreshPalette(sender) {
return function (evt) {
var colorPicker = sender;
var selectedColor = colorPicker.get_selectedColor() || "#808080";
colorPicker._updateHslPaletteElementsUI(colorPicker._getRgbFromHex(selectedColor), null, true);
};
}
</script>
For the time being you can safely use the same scenario with ContentAreaMode set to Div.
For all controls that have a dropdown, there should be a DropDownSettings part. Namely, it should control: width, height as well as their min / max counterparts and css class. Perhaps z-index
There are several other suggestions along these lines, but in general, Telerik needs to make their data input controls more consistent in the implementation of a "Label" property. Without such consistencies, it makes including controls that have this property and those that don't together on the same page much more difficult. As of the writing of this, the DropDownList and DatePicker controls do not have a Label property. There is no apparent reason why this should be so. All of the input controls should have this property. Related requests: http://feedback.telerik.com/Project/108/Feedback/Details/149658-add-built-in-label-to-control http://feedback.telerik.com/Project/108/Feedback/Details/66117-add-label-property-to-ajax-raddatepicker Related annoyed forum thread about the omission of this property in the DropdownList control: http://www.telerik.com/forums/dropdownlist-label#TI3zWYeMFESXjPIY_bYjZg
The editor does not go to edit mode. The problem occurs also when Auto mode is used. This prevents the developers to rely on the AutoResizeHeight functionality when a mix of all rendering modes is required. Possible workaround is to use the RadDeviceDetectionFramework - http://docs.telerik.com/devtools/aspnet-ajax/controls/raddevicedetectionframework - and programmatically disable the AutoResizeHeight in mobile devices: ASP.NET <telerik:RadEditor ID="RadEditor1" runat="server" RenderMode="Auto" AutoResizeHeight="true"> <Content> <p>editor</p> </Content> </telerik:RadEditor> C# using Telerik.Web.Device.Detection; public partial class Default : System.Web.UI.Page { private void Page_Load() { if (Detector.GetScreenSize(Request.UserAgent) < DeviceScreenSize.Medium) { RadEditor1.AutoResizeHeight = false; } } }
There is a missing label in the Box tab (Width and Height options) in the StyleBuilder dialog. You can dynamically change the label by following this example: <telerik:RadEditor runat="server" ID="RadEditor1" OnClientCommandExecuted="OnClientCommandExecuted"> <Tools> <telerik:EditorToolGroup> <telerik:EditorTool Name="StyleBuilder" /> </telerik:EditorToolGroup> </Tools> </telerik:RadEditor> <script> function OnClientCommandExecuted(sender, args) { var command = args.get_commandName(); if (command === "StyleBuilder") { var dialog = sender.get_dialogOpener()._dialogContainers[command]; dialog.add_pageLoad(fixSectionName); } } function fixSectionName(sender, args) { var dialogWin = sender.get_contentFrame().contentWindow; var label = dialogWin.$telerik.$(".reStyleBuilderBoxSize").find("legend"); label.html("Dimensions"); } </script>
I am doing a bin deployment on a web site for the following assemblies... Telerik.Windows.Documents.Core Telerik.Windows.Zip Telerik.Windows.Documents.Fixed Telerik.Windows.Documents.Flow Telerik.Windows.Documents.Flow.FormatProviders.Pdf Telerik.Windows.Documents.Spreadsheet Telerik.Windows.Maths Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf I recently used the upgrade wizard, and it successfully updated the versions for these assemblies, but it did not update the version numbers in the Web.config. I manually removed the version number completely from Web.config, and it seems to work fine.
When RadEditor with Bootstrap skin is inserted in the ContentTemplate of RadWindow, the tools look incorrect. A temporary solution is to override some CSS rules with more proper values: <style> .RadWindow .RadEditor .Bootstrap.reToolbarWrapper .reToolbar .reToolLastItem .reTool { border-right-width: 0; } .RadWindow .Bootstrap.RadEditor.reWrapper .reSplitButton.reTool { width: 42px; } .RadWindow .Bootstrap.RadEditor.reWrapper .Bootstrap.reToolbarWrapper .reToolbar li { border-right-width: 1px; border-left-width: 0; } .RadWindow .Bootstrap.RadEditor.reWrapper .Bootstrap.reToolbarWrapper .reToolbar li.reToolFirstItem { border-left-width: 1px; } .RadWindow .Bootstrap.RadEditor.reWrapper .Bootstrap.reToolbarWrapper .reToolbar .reSeparator + li { border-width: 1px; } </style> <telerik:RadWindow runat="server" Width="1200px" Height="600px" VisibleOnPageLoad="true"> <ContentTemplate> <telerik:RadEditor runat="server" Skin="Bootstrap"> </telerik:RadEditor> </ContentTemplate> </telerik:RadWindow>
The text in the tabs' titles of the Sliding panes of the Splitter control are not properly rotated. Can be reproduced here: http://demos.telerik.com/aspnet-ajax/splitter/examples/overview/defaultcs.aspx http://demos.telerik.com/aspnet-ajax/splitter/examples/sp_firstlook/defaultcs.aspx
When adding a link with a class name, the Unlink command cannot remove the formatting. Temporary solution is to clear anchor's classes programmatically via the ApplyClass command: <telerik:RadEditor runat="server" ID="RadEditor1" OnClientCommandExecuting="OnClientCommandExecuting"> <Content> <a href="http://www.telerik.com" class="my-class">link</a> </Content> </telerik:RadEditor> <script type="text/javascript"> function OnClientCommandExecuting(sender, args) { var command = args.get_commandName && args.get_commandName(); if (command === "Unlink") { var myArgs = new Telerik.Web.UI.EditorCommandEventArgs("ApplyClass", null, ""); sender.fire("ApplyClass", myArgs); } } </script>
I love WebForms and the wealth in the Toolbar. I would like to write the payload of the web page in a webform and limit the round tripping with micro webservices, so there is no PostBack. Which means I can do more clientside in a KendoUI style. This would address the criticism of the bloat that comes with ViewState in webforms offering a leaner web page, but with all the advantages of the JavaScript tooling. For the most part a lot of this can be done already, would just prefer not to have any limitations in the controls that I can use for this. Just that there is such a driver now with the fashion of AngularJS/SPA applications suggesting that webforms cannot compete here.