Data Shuttle converting mmm d, yyyy date format to numerical value

Paul M Kahl

Hello Everyone,

I have a Data Shuttle workflow that has been run virtually every business day for over a year. When running today, four columns of dates converted to numerical values.

No formatting of the source sheet has changed (Excel file with a Custom category of mmm d,yyyy

Cell history confirms date format used to be present

The existing columns are configured to Auto in Data Shuttle, but I created two new columns to test columns types of Text and Number, but they do the same thing.

Changing the format of the cells in the Excel resolves the issue, but I cannot find the clue to how it worked prior to today.

Anyone experiencing this issue?

polinkuer12

python

from datetime import datetime

date_string = "Sep 15, 2022"

date_object = datetime.strptime(date_string, "%b %d, %Y")

numerical_value = date_object.toordinal()

print(numerical_value)

richards123

Private Sub Worksheet_Change(ByVal Target As Range)

  If Not Intersect(Target, Columns("E:F")) Is Nothing Then  'Change Date format to dd-mmm-yy
  
        If Not IsDate(Target.value) = False Then
         
         Target.NumberFormat = "dd-mmm-yy"
         
         End If
       End If

End Sub

Yves

Hey Paul,

Im having the exact same issue, apart from, mine is stopping the data shuttle altogether. Due to the column being a "Date Only" column. It's not populating at all. Would be great to hear how you got around this :/

Paul M Kahl

Hi Yves,

I ran a new set of tests today and I am no longer seeing the conversion to a numerical string.

I changed nothing on my side in either the mmm d,yyyy formatting in the source excel, or in the destination column. Note, my destination column is a date column but it is not restricted…

Looking at your error, I'm wondering if your is set to restrict to dates only. I recall seeing that as in issue.

Paul M Kahl

I take it back, the same error occurred while running in production today

Danielle Wilson

Hi @Paul M Kahl - I checked with our product team and that's definitely unexpected behavior, if you could submit that to Support!