igx grid date column exporting to excel as text instead date

State Not Answered
Replies 3 replies
Subscribers 8 subscribers
Views 1645544 views
Users 0 members are here

185

igx grid date column exporting to excel as text instead date

arsv M posted over 3 years ago

Hi,

I have date column on igx grid with date filter with column data as (6/30/2021, 3/16/2020....).

While exporting to excel this date column is exporting as text in excel (shows text filter in excel column).

Please advise.

Parents

740

Offline Martin Evtimov posted over 3 years ago
Hi,

Thank you for contacting Infragistics Community!

I believe you will find the Export to Excel topic in our official documentation very helpful. As you can observe within the first example of this topic you can export the igxGrid to Excel. Once you do this, you will find that the values in the OrderDate column are of type Date and that the correct date filtering strategy is being used. Having this in mind, I assume two possible reasons for the described behavior:

the ‘date’ dataType property is not provided to the igxColumn

an older version of IgniteUI for Angular package is used

In case that you are using IgniteUI for Angular 12.x, have the dataType property set to 'date' and the issue still persists I suggest modifying the following sample so that it reproduces the described behavior and send it back to me. This will give me the opportunity to debug it on my side and to provide you with solution as soon as possible.

Looking forward to hearing from you.

Best Regards,
Martin Evtimov
Associate Software Developer
Infragistics, Inc.
Cancel
Reply

Cancel
185

Offline arsv M posted over 3 years ago in reply to Martin Evtimov

I am on "igniteui-angular": "^8.2.3",

Below is my igx column:

<igx-column field="AsOfDate" header="As of Date" [dataType]= "'date'" [formatter]="formatDate">

    </igx-column>

public formatDate(val: Date) {

    const options = {month: '2-digit', day: '2-digit', year: 'numeric'};

    return new Intl.DateTimeFormat('en-US', options).format(val);

  }

Is there work around for for this instead of updating to newer version?
Cancel
Reply

Cancel

Reply

740

Offline Martin Evtimov posted over 3 years ago in reply to arsv M

Hi,

Thank you for getting back to me!

Please note that according to our policy support is applicable to two versions back - latest stable, and the previous major version (currently 11.1.x and 12.1.x). Having this in mind version 8.2.31 can be considered retired and it is no longer eligible for Developer Support Services. This means that some of the features and bug fixes introduced within IgniteUI for Angular version 9 and above won’t be available. Bug fixing and support tickets are not applicable for version 8.2.31 as well.

In order to take advantage of all new features, functionalities and developer support I would suggest updating your application to Angular 12 and using Ignite UI for Angular 12.1.x, which currently is the latest available. For more information, you can refer to our official Update guide.

In case you want to stick to version 8, here you can find the source code of IgniteUI for Angular 8. I believe you will find it very helpful in order to investigate the root cause of the described behavior and to find a workaround for it.

Please let me know if you have any further questions.

Best Regards,
Martin Evtimov
Associate Software Developer
Infragistics, Inc.
Cancel
Reply

Cancel

Children

No Data