Issues woth Date Fields when importing/exporting Excel files via the Translator?

We have added several date fields to the Issues Object, and have them formatted for dates. It all works well until we use the Translator to try and export/update, then import.... we end up with dates in PV and/or the spreadsheet that look like this: 40444. (Which is what Excel shows if we switch the cell's format to General, instead of date.)

Has anyone else had to deal with this? We've tried various combinations of formatting options, but no luck (and we want to keep the date format edits in PV, for data integrity reasons...)

Find more posts tagged with

BPM

Comments

Matt_Michael

Hi Pat,

Which version of ProVision are you using? Also, I have seen other users implement the 'Text' data type for custom properties to overcome issues with the Date data type in the past.

Regards,

Matt Michael

pat bleasdale

Hi, Matt,

We are using 6.1.3. Is that a taco in your little picture? What's with that?

Matt_Michael

Hey Pat,

There was a bug when operating with the Date data type in ProVision and exporting to Translator in v6.1.3, which has been addressed in v6.2.x.

Yup, it's a Taco. I happen to really like tacos, and since there weren't any pictures of hotsauce I decidied to use this.

Cheers,

Matt

pat bleasdale

Ohhh, what's your position on guacamole? Is the current version of PV 6.2.2? When will 6.3.3 be out?

Matt_Michael

Hey Pat,

I generally prefer fresh Avacado slices to Guacamole.

The current version is indeed v6.2.2, we plan to have v6.2.3 out late in September.

Regards,

Matt Michael