We are using the ETL tool to pull CSD tables from the Data Lake. Date fields are coming across in XXXX-XX-XX (Year-month-day) format; however they appear to be character strings as opposed to a date datatype. We are using Hyperion as our BI. Hyperion sees the date fields as string, not date, and this limits the usefulness of the data. We are able to convert the data type in our SQL database to date and Hyperion then sees the date fields as date as well; however, when we extract new data from the DL to append to our SQL database, there are conflicts with the field types.
We are looking for options to address this issue without having to create an additional time consuming data transformation process during the extract and append process. We are trying to keep the data as current as possible with frequent extracts, and are trying to keep things efficient. Perhaps there is a way to deal with this with the Hyperion connection? Any suggestions would be appreciated.