CSVRenderer - Date style is not enforced on render\export

Aspose.Cells Product Family
33

Hi Shakeel,
In the report definition, when we have a rate field value used in a cell, we use the fomat “P” for the format of the same cell (format property of the cell). so if the value in the data is “0.03433” than the output should look like “3%”.
As i mentioned previously, we also put the “Culture” value in the Language property of the cell. The Culture parameter is a report input and we populate it at report runtime by the UI user who runs the report but nevertheless, i do not understand why it affects the value in the output csv when it comes to a rate type field.

In addition, I have another open SR for improper CSV structure.
please check the screen shot.

I see for example line numbers on places that should not start a usual seen CSV line record. I can also identify columns that have a “coma” in their values and these should normally be warped in quotes for the column value to parse right.

Needless to - we are working with Aspose.Cell SSRS V1.9 for over 6 years now and for very long time we did not get these type of issues. Can we trust that the new version to support all the capabilities and fixes from previous versions?

Since we have complaining customers awaiting on a fix here, can you please also share an ETA - the time it will take you to provide a fixed version of the product ?

Thanks
BoazG, Sizmek

34

@boaz.goldstein

Thanks for considering Aspose APIs.

We have logged your comment in our database for product team consideration and investigation. Once, we will have some fix or any other update for you, we will let you know asap.

35

@boaz.goldstein

We have found the issues and fixed them.

Please try the fixed version i.e. Aspose.Cells for Reporting Services 2012 V17.8.2.

Copy Aspose.Cells.ReportingServices.DLL into ${Report Server}/bin/ folder and export report file again.

If you still face the issues, please inform us. We will check it ASAP.

36

hi Sahkeel,
thanks for the update.
I encounter ERROR strings in result CSV file when using en-ES culture in the report
see attached 3 examples for CSV files using the Aspose: 2 using the new version you provided, 1 using the previous version 17.8.0.2
Aspose Tests 17.7.2.0.zip (28.6 KB)

Your quick response is very much appreciated.

thanks BoazG, Sizmek

37

@boaz.goldstein

We were able to observe the problem relating to en-ES culture and logged your comment in our database. We will evaluate it and fix the issue. Once, there is some news for you, we will update you asap.

38

thank you Shakeel !

39

@boaz.goldstein

Please try the fixed version

If you still face the issues, please post report definition description of error field here. We will check it ASAP.

40

hi Shakeel,
thanks.
i have tested version 17.8.3 you have sent and still the #Error message in date fields persists - when a report is running with culture = “en-ES”. when the same report runs with the default culture “en-US” date fields looks alright!.
Apart to the #Error message, all other formatting and output looks good! yet - this is not enough. we need to be able to support all cultures.
by the way - when testing with en-AU (Australia) the results are good!
the same goes for hebrew (he-il).

Please try and provide immediate assistence.

attaching all result tests
17.8.3.zip (38.2 KB)

thanks
BoazG, Sizmek.

41

@boaz.goldstein

We saw the problem as you have described and logged it.

But we asked you this and you did not provide it. Please provide it so that we could fix this issue properly.

42

Hi Shakeel,
what setting are you looking for?
In the RDL itself we see error in 2 locations:
image.png (90.2 KB)

The yellow mark in the screenshot is header, the red circles are date data values in each row (i did not mark all rows).
We use a set of text boxes for the header, where each text box is a different expression that results in the value you see in the report. We do not use the language property of the text box, we do use the culture input parameter for the format of the result line.again - how come it works correct for multiple culture (languages) but not for en-ES ?

here is example for expression of the first text box with the #Error:
=Code.GRH.GetText(“Campaign_Dates”,“Analytics_RDLs”, Parameters!SystemLanguage.Value) + iif(Parameters!IsPreviewReport.Value=CInt(1),"",iif((Parameters!ReportFlag.Value And 1)=1,ReportsHelper.RdlHelper.ConvertDateToString(First(Fields!CampaignStartDate.Value, “HeaderDS”),Parameters!Culture.Value,“d”) & " - " & ReportsHelper.RdlHelper.ConvertDateToString(First(Fields!CampaignEndDate.Value, “HeaderDS”),Parameters!Culture.Value,“d”) & " (" & Code.GRH.GetText(“TimeZoneLookup_” & First(Fields!TimeZoneID.Value, “HeaderDS”) ,“ACM_Lookups_Lookups”, Parameters!SystemLanguage.Value) & “)”,“N/A”))

As you see, we use external code to interpret the date we do use the parameters:

  • Parameters!SystemLanguage.Value
  • Parameters!Culture.Value

We use the Culture param to set the format, the language param is always english (en-US).

For the red marked values - it is the row value in the date column which is a simple date field, which is using the “culture” propery of the field.

Let me know if you need additional information.

Thanks
BoazG, Sizmek

43

@boaz.goldstein

Thanks for detailed information and clarification. It will help us look into this issue and fix it. We have logged this post in our database for product team investigation. Once, we will have some news or fix for you, we will update you asap.

44

@boaz.goldstein

Please download and try the following fix and let us know your feedback.

If you still face any issue, inform us. We will check it ASAP.

45

Hi Shakeel,
Thanks ! have not yet tested the new fixed version but i want to make sure of something:
Any new version that you provide contains all fixes you added in the previous versions right ???

thanks
Boaz

46

@boaz.goldstein

You are right. It contains previous fixes as well.

47

hi Shakeel,
I have tested the new version and found that it did manage to remove the “#Error” strings all across the result txt\csv file, The result file looks correct and the date strings are formatted perfectly.
for now we look good!
thanks for the effort and i will further update you if you encounter more issues.

Thanks
BoazG, Sizmek

48

@boaz.goldstein

Thanks for your feedback and sharing good news with us. Let us know if you face any other issue, we will be glad to help you further.

49

A post was split to a new topic: Badly formatted reports looks like CSV rendered them not ACTXT

50
51

The issues you have found earlier (filed as CELLSRS-514) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by Amjad_Sahi

52

The issues you have found earlier (filed as CELLSRS-515) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by Amjad_Sahi