Hi Team,
Posting on behalf of John Cowles for Appian.
If you are importing date/time fields into Gainsight and getting null values, there are two separate things going on that are worth understanding.
First, any date/time field that carries timezone information, such as EDT or EST, will not ingest directly. This is expected behavior. Ingesting date/time values with timezone info is unsupported by design, so those fields come through as null whenever a timezone is present. To bring these values in, the timezone component needs to be removed from the source data before import.
Second, the common workaround of importing the value as a string and converting it with the To Date function has recently stopped working for some files. When a CSV contains mixed date formats, meaning months and days that appear with both one and two digits, the To Date formula fails to convert the string into a date. Gainsight has identified this as a product bug in the logic that parses strings into dates. Engineering has acknowledged it and a fix is in progress, and there is no reliable workaround at this time.
The short version is that the timezone behavior is a design limitation rather than a defect, while the To Date parsing failure is a confirmed bug that is actively being worked on.
~Andrew A