Parser Error Message: 'EncodingConverter' is unable to convert 'System.Text.UTF8Encoding' to 'System.ComponentModel.Design.Serialization.InstanceDescriptor'.
Source Error:
|
19 Answers, 1 is accepted
Rank 1
It's a bug in the control's markup....
<XmlaConnectionSettings Encoding="utf-8"></XmlaConnectionSettings>
Remove the encoding reference and the problem diappears.
Thank you for contacting us.
Our developers are aware of this issue and will introduce a fix for the future releases. Currently, you can use the following approach to work around the issue:
protected void Page_Load(object sender, EventArgs e){ RadPivotGrid1.OlapSettings.XmlaConnectionSettings.Encoding = System.Text.Encoding.UTF8;}Hope this helps. Please excuse us for any inconvenience this might have caused you.
Regards,
Eyup
Telerik
Rank 1
Ed
Rank 1
Rank 1
Mensaje de error del analizador: 'EncodingConverter' no puede convertir 'System.Text.UTF8Encoding' en 'System.ComponentModel.Design.Serialization.InstanceDescriptor'.
Error de código fuente:
LÃnea 1: <%@ Page Language="VB" AutoEventWireup="false" CodeFile="Reports.aspx.vb" Inherits="Reporte_Reports" %>
LÃnea 2:
LÃnea 3: <%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %>
Archivo de origen: /Reporte/Reports.aspx LÃnea: 1
Rank 1
RadPivotGrid.OlapSettings.XmlaConnectionSettings.Encoding = System.Text.Encoding.UTF8
Server Error in '/' Application.
Error Analyzer
Description: Error parsing a resource required to service this request. Please review the specific error details and modify the analysis of source code appropriately.
Parser Error Message: 'EncodingConverter' can not convert 'System.Text.UTF8Encoding' in 'System.ComponentModel.Design.Serialization.InstanceDescriptor'.
Source Error:
Line 1: <% @ Page Language = "VB" AutoEventWireup = "false" CodeFile = "Reports.aspx.vb" Inherits = "Reporte_Reports"%>
Line 2:
Line 3: <% @ Register Assembly = "Telerik.Web.UI" Namespace = "Telerik.Web.UI" TagPrefix = "telerik"%>
Source File: / report / reports Online: 1
Can you please verify whether you have removed the setting from the mark-up definition of the grid?
Looking forward to your reply.
Regards,
Eyup
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Rank 1
The above did not work for me. How would one go about removing the setting from the markup definition of the grid?
Shannon
Just make sure that you are NOT setting it declaratively in the mark-up definition of RadPivotGrid located in the aspx page:
<OlapSettings> <XmlaConnectionSettings Encoding="utf-8"></XmlaConnectionSettings></OlapSettings>Please check whether the snippet above is present in your code and remove it.
Regards,
Eyup
Telerik
See What's Next in App Development. Register for TelerikNEXT.
Rank 1
Rank 1
Can you ***PLEASE*** fix this?
It's still an issue in latest release 2017.1.228
I am afraid this behavior is not planned to change. Please set the mentioned property programmatically in the code-behind as demonstrated already in the thread:
protected void Page_Load(object sender, EventArgs e){ RadPivotGrid1.OlapSettings.XmlaConnectionSettings.Encoding = System.Text.Encoding.UTF8;}Regards,
Eyup
Telerik by Progress
Rank 1
While I understand this is a workaround, this really needs to be fixed in the designer.
When this error is encountered, it is not obvious what happened:
Parser Error Message: 'EncodingConverter' is unable to convert 'System.Text.UTF8Encoding' to 'System.ComponentModel.Design.Serialization.InstanceDescriptor'.
This takes a while to remember what the cause is, and in addition, adding this code into every page's code behind is not a good solution.
I am afraid that, as explained in my colleague Eyup, this improvement is not planed for implementation in the current Roadmap of the PivotGrid. The optimal suggestion I can give you in this case is to submit a feature request for this improvement into our FeedBack portal. If many people are interested in it (and respectively the vote count is high) this will increase the priority of the item and our Product Manager will consider adding this feature for implementation shortly:
https://feedback.telerik.com/Project/108/Feedback/List/Feature%20Request
Regards,
Vessy
Telerik by Progress
Rank 1
From September 20, 2013
"Our developers are aware of this issue and will introduce a fix for the future releases"
It sounds as if it is planned.
Is there really a current road map for PivotGrid? I haven't seen anything besides compatibility/bug fixes in a long time.
Hi John,
The UI for ASP.NET AJAX is a pretty mature product and the roadmap is currently based on enhancing the controls stability, to improve and unify the appearance of the different components along with better documentation and how-to articles.
I searched for this PivotGrid request in the public portal and wasn't able to find such. This unfortunately means that we cannot measure it and raise its priority in the backlog. Can you please log your inquiry in the feedback portal as suggested by Vessy on Mar 15 - http://www.telerik.com/forums/pivotgrid-problem#qkG-08awVU2oxhzvK0dmCA?
Best regards,Rumen
Progress Telerik
Rank 1
Hello Rumen,
Thank you for the reply.
I am unsure why I have to submit a known issue to a request queue. Especially one that was acknowledged about 4 years ago as being fixed soon.
Can you please explain why I have to do this? If so, please do.
John
Hi there,
I agree with you that this is a known issue, but its priority is low due to that only a few users have requested it during the years and there are suggestions of how to overcome it. The chance to get implemented will become higher if the issue is logged by a customer in the feedback portal and the people can vote for it and raise its status in the backlog.
Best regards,Rumen
Progress Telerik
Rank 1
Same here.
Just started using pivotgrid.
Out of the box it is wrong, so applied work-around.
Do you recommend another way to go for Web dev, instead of ajax.