Olap Client Exporting when using paging showing only paged results

[Brett Macpherson]

Hi,

    i've setup an olapclient control into my project and enabled paging to assit with some of the larger data sets rendering slow. However now when i export the data it only exports the paged data and not the entire cube. this behaviour is also observed on your demo website of the control. How can i still have paging enabled but export the entire cube?

[Saranya Sivan]

Hi Brett Macpherson, 

  

Thanks for contacting Syncfusion support. 

  

We would like to inform that you can export the complete data by enabling the `EnableCompleteDataExport` property. Please find the UG and sample below. 

  

UG: https://help.syncfusion.com/aspnet/pivotclient/olap-client-exporting#exporting-customization 

  

Sample: https://www.syncfusion.com/downloads/support/directtrac/general/7z/SyncfusionASPNETApplication1-1136976660 

  

Please let us know if you have concerns. 

  

Regards, 

Saranya. 

[Brett Macpherson]

ahh there it is, i swear i looked but there it is. Sorry for bothering you i should of been able to find this myself.

So I enabled this in the EnableCompleteDataExport="true" option and it gets upset sending the error below. It was working fine and all i did was to add that option in the ej:pivotClient control line. Is there something else to do? I found i got this error if I had conditional formatting enabled and tried to export also, which i got around by disabling it on the beforeExport event. is there something like that which will need to happen?

<Error>

<Message>An error has occurred.</Message>

<ExceptionMessage>Type 'System.String' is not supported for deserialization of an array.</ExceptionMessage>

<ExceptionType>System.InvalidOperationException</ExceptionType>

<StackTrace> at System.Web.Script.Serialization.ObjectConverter.ConvertListToObject(IList list, Type type, JavaScriptSerializer serializer, Boolean throwOnError, IList& convertedList) at System.Web.Script.Serialization.ObjectConverter.ConvertObjectToTypeInternal(Object o, Type type, JavaScriptSerializer serializer, Boolean throwOnError, Object& convertedObject) at System.Web.Script.Serialization.ObjectConverter.ConvertObjectToTypeMain(Object o, Type type, JavaScriptSerializer serializer, Boolean throwOnError, Object& convertedObject) at System.Web.Script.Serialization.ObjectConverter.ConvertDictionaryToObject(IDictionary`2 dictionary, Type type, JavaScriptSerializer serializer, Boolean throwOnError, Object& convertedObject) at System.Web.Script.Serialization.ObjectConverter.ConvertObjectToTypeInternal(Object o, Type type, JavaScriptSerializer serializer, Boolean throwOnError, Object& convertedObject) at System.Web.Script.Serialization.ObjectConverter.ConvertObjectToTypeMain(Object o, Type type, JavaScriptSerializer serializer, Boolean throwOnError, Object& convertedObject) at System.Web.Script.Serialization.ObjectConverter.ConvertObjectToType(Object o, Type type, JavaScriptSerializer serializer) at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit) at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize[T](String input) at Syncfusion.JavaScript.PivotClient.ExportPivotClient(OlapDataManager DataManager, String args, String fileName, HttpResponse response) at Solutek.Spire.Web.OlapController.Export() in e:\SPIRE\Main\Solutek.Spire.Web\OlapController.cs:line 720 at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClassf.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.Execute(Object instance, Object[] arguments) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.<>c__DisplayClass5.<ExecuteAsync>b__4() at System.Threading.Tasks.TaskHelpers.RunSynchronously[TResult](Func`1 func, CancellationToken cancellationToken)</StackTrace>

</Error>

[Saranya Sivan]

Hi Brett Macpherson,  

  

We can able to reproduce the issue at our end and now we are validating the complexity of its fix. So we will update you the timeline on tomorrow (22 April 2021). 

  

Regards, 

Saranya S. 

[Manikandan Murugesan]

Hi Brett, 

Currently, we don’t have support to export pivot grid with conditional formatting. But we should avoid the reported exception. So, we have considered this as a bug “Exception occurs while export with conditional formatting” and logged a defect report in our database. And the fix will be available in Vol 1 SP1 release which is estimated to be rolled out in the mid of May, 2021. You can track the same by using below link. 

 

https://www.syncfusion.com/feedback/24623/exception-occurs-while-export-with-conditional-formatting 

Please let us know if you have any concerns. 

Regards, 

Manikandan. 

[Brett Macpherson]

Hi Saranya,

                  just to ensure we're on the same page. I'm not that concerned about exporting with conditional formating causes an issue, i just referenced it as it produces a similar error. In my beforeExport function i explicidly disable conditional formating to avoiid the error. The main issue i'm reporting and would like corrected it that when i enable the "EnableCompleteDataExport" option it generates the error below and i am unable to export the complete pivot table, only the pages of it. This is the bug that i am reporting.

Regards,

Brett

[Manikandan Murugesan]

Hi Brett, 

 

Please find the response below. 

Query	Comments
I'm not that concerned about exporting with conditional formatting causes an issue, i just referenced it as it produces a similar error. In my beforeExport function i explicitly disable conditional formatting to avoid the error.	The conditional formatting couldn’t be disabled by the property ‘exportWithStyle’ in ‘beforeExport’ event. And it can be disabled only in report.
The main issue I’m reporting and would like corrected it that when i enable the "EnableCompleteDataExport" option it generates the error below and i am unable to export the complete pivot table, only the pages of it. This is the bug that i am reporting.	When paging or virtual scrolling, to export all the pages, we should enable the property “EnableCompleteDataExport”. It works fine at our end. Please refer the below sample.    Sample: https://www.syncfusion.com/downloads/support/directtrac/general/7z/SyncfusionASPNETApplication1-1136976660    As we said in our previous update, we have a issue in the above feature when we apply conditional formatting and we have logged bug report for that. So, disable the conditional formatting to export all the pages.     If still the problem exists, kindly reproduce the problem in the above provided sample and revert us (or) send your sample that replicating the problem. This would be a very helpful for us to investigate the reported problem at our end and provide the solution at earliest.

 

Please let us know if you have any concerns. 

 

Regards, 

Manikandan. 

[Brett Macpherson]

Hi Manikandan,

                 thanks for clearing that up. I had a line (this._pivotGrid.model.enableConditionalFormatting = true; ) in my RenderSuccess function and it seems as though trying to turn on conditional formating there breaks it, i think i had it there hoping that it would load the conditional formatting when loading the report. I removed that line and only enable if the user presses the button and turn it off before exporting which appears to be a work around for the issue. 

A side question i've noticed that with paging turned on the totals no longer appear, which thinking about it makes sense as i'm imagining the totals happen client side and you don't have all the data for the totals when paged. But if there is only 1 page of series/categorical is there a way to get it to show the totals? and only hide the totals if there is more than 1 page. I really like the GridLayout="ExcelLikeLayout" setting displays totals and if it could show totals when there is only 1 page it would be mint.

Regards,

Brett

[Manikandan Murugesan]

Hi Brett, 

This is the default behavior of the pivot grid component. We won’t display total cell’s when the paging is enabled. 

Please let us know if you need further assistance on this. 

Regards, 

Manikandan. 

[Brett Macpherson]

ok no worries, thanks for the info.

I ended up adding a button that will allow the user to switch between paging and showing totals.

[Saranya Sivan]

Hi Brett Macpherson, 

  

Thanks for the reply. 

  

Please let us know if you have any other queries. We are always happy to assist you.  

  

Regards, 

  

Saranya S. 

 

[Manikandan Murugesan]

Hi Brett, 

We are glad to announce that our Essential Studio 2021 Volume 1 Service pack v19.1.0.63 is rolled out where the reported issue has been fixed. It is available for download under the following link. 

https://www.syncfusion.com/forums/165437/essential-studio-2021-volume-1-service-pack-release-v19-1-0-63-is-available-for-download 

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 

Regards, 

Manikandan