Forum Discussion

rainerpowerbi's avatar
rainerpowerbi
Resolver I
4 years ago

Excelexport: Problem by date-fields

Hi,

I think there is a bug in an option of the excel-export.

Example:
- I work in Germany with german date/time-settings

The Report-column(as the SQL-Table) contains following field: (1. February 2022)



If I export this with the following option (data with present layout) within Excel I see following value:

 

EXCEL: wrong !



I could format this column within Excel so that the value would be correct but this no option for the end-user.

-----------------


If I export this with the following option I get within Excel the correct value:

 

EXCEL: correct !



Is it a bug ? Is there a further solution ?

The new Export with layout is very well but the values in Excel have to be correct without further formattings by the end-user.

Please help.

 

Kind regards

Rainer

 

 



 

 



 

2 Replies

  • v-zhangti's avatar
    v-zhangti
    Community Support

    Hi, rainerpowerbi 

     

    For all the visuals in PBI we need to choose “Summarized data” option instead of “Data with current layout”.

    The summarized data will give you the formatted output with all the columns as is. However the data with current layout will export the underlined data and especially with the table visuals with date it mess up.

     

    There are Export data options available, depending on your need you need to choose one of them. 

     

    Best Regards,

    Community Support Team _Charlotte

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • rainerpowerbi's avatar
      rainerpowerbi
      Resolver I

      Hi Charlotte,

      I tested your hint:

       

       

      But...the bug is still there:
      The shown value is still 1.2.22 instead of 1.2.22

      WRONG:

       

      The  new LAYOUT-EXPORT-OPTION is normally very good especially for MATRIX-Export.

      I think the reason could be the German-settings in Excel but I think that a few weeks ago this problem did not exist.

      Kind regards

      Rainer