We have added a custom data field for use in Ticket Orders.
The problem is that it only saves 12 characters to the T_Order table.
I ran a SQL Profiler on the order save and found the following:
UPDATE T_ORDER SET order_no = 1847029, transaction_no = 634807, custom_1 = 'Collect Conn' WHERE order_no = 1847029
The code is truncating my custom data field (custom_1). It allows 255 characters in the t_order table, and so I don't know why it is doing this. It doesn't seem to be part of a Stored procedure and therefore I can't find where to look at the code.
Thanks,
- Blair
Hi Blair
Does this custom field use a dropdown to select the value instead of typing it in? If so, this is what is causing the issue.
If you are using a dropdown, I am guessing that you have stored the values in t_kwcoded_values? To get around the truncation I use the id from t_kwcoded_values as the value to be stored in t_order and description is what is displayed. In the order you see the description, but it does mean linking back to t_kwcoded_values if I want to output the description elsewhere.
Hope that helps.
Sandra
Hi Sandra,
That works to store the id value.
But we are using it as an Element in a Header (Ticket Design) and I don' t see how I can link back to t_kwcoded_values as properties for that element (Custom Data 1) only allows me to link to the custom_1 column in t_order.
Or, is there something I am missing?