Hello,
I'm experiencing an issue with the formatting of Datetime fields in custom attribute values stored in TX_CUST_KEYWORD and defined in T_KEYWORD.
We have a Local Procedure (LP) that writes a date into a TX_CUST_KEYWORD row, together with the customer_no and keyword_no.
When the Local Procedure runs it takes an XML payload containing a datetime like "2023-05-02 14:00:00" and inserts a new row into TX_CUST_KEYWORD. The LP then executes a SELECT statement which queries TX_CUST_KEYWORD to get the values that have just been written. The output of this query is a string such as "May 2 2023 2:00PM", which is the same date/time as was send to the LP. The LP date variable is configured as an SQL "datetime", although I'm not certain how the T_KEYWORD has been set up.
However when viewing the data from within Tessitura, we see the default date of "01/01/1990".
Could this be a configuration issue for the T_KEYWORD field, or perhaps a presentation issue where we need to configure some formatting for the visual output in Tessitura?
Any advice gratefully received.
James,
I assume you are viewing in Tessitura on the Attribute tab/radio button. Given that the date is showing in date format, I would THINK the T_KEYWORD set-up is correct, however it never hurts to check. Our attribute date elements have both the "Data Type" and "Edit Mask" set to "Date"; presumably yours would as well.
I think the issue might lie in the data itself inserted into TX_CUST_KEYWORD. I cannot speak to the system as a whole, but I can confirm that all of our date attributes are date ONLY, no timestamp. So, given your example above, the entry in the "key_value" column of TX_CUST_KEYWORD would be "2023-05-02" with nothing else. At least, that seems to work for our date elements. If you really NEED the timestamp, I am not sure; maybe someone else knows more than I as to how one would format that, but if you are okay to abandon the timestamp, that should work.
Hope that helps,
John A. Moskal II