[Vtigercrm-developers] Has anyone else had a problem with a user's date format preference interfered with a custom datetime field?

Tue Dec 24 17:46:59 GMT 2024

After adding some extra debug messages, the date format conversion is
occurring, just not being passed to the query.

2024-12-24T11:41:20-06:00 DEBUG VT *Entering
> getValidDBInsertDateValue(12-24-2024) method *...
> 2024-12-24T11:41:20-06:00 DEBUG VT *Entering
> convertToDBFormat(12-24-2024) method* ...
> 2024-12-24T11:41:20-06:00 DEBUG VT* __convertToDBFormat is returning
> '2024-12-24'*
> 2024-12-24T11:41:20-06:00 DEBUG VT Exiting getValidDBInsertDateValue
> method ...
> 2024-12-24T11:41:20-06:00 DEBUG VT Entering function get_column_value
> (cf_817, , cf_817, 21, V='')
> 2024-12-24T11:41:20-06:00 DEBUG VT Exiting function get_column_value
> 2024-12-24T11:41:20-06:00 DEBUG VT Entering function get_column_value
> (cf_823, , cf_823, 16, V='')
> 2024-12-24T11:41:20-06:00 DEBUG VT Exiting function get_column_value
> 2024-12-24T11:41:20-06:00 DEBUG VT Entering function get_column_value
> (cf_841, , cf_841, 21, V='')
> 2024-12-24T11:41:20-06:00 DEBUG VT Exiting function get_column_value
> 2024-12-24T11:41:20-06:00 DEBUG VT Entering function get_column_value
> (cf_980, , cf_980, 21, V='')
> 2024-12-24T11:41:20-06:00 DEBUG VT Exiting function get_column_value
> 2024-12-24T11:41:20-06:00 DEBUG VT Entering function get_column_value
> (internal_comment_was_added, , internal_comment_was_added, 1, V='')
> 2024-12-24T11:41:20-06:00 DEBUG VT Exiting function get_column_value
> 2024-12-24T11:41:20-06:00 DEBUG VT Prepared sql query being executed :
> UPDATE vtiger_ticketcf SET cf_825=?,cf_815=?,cf_779=?,cf_833=? WHERE
> ticketid=?
> 2024-12-24T11:41:20-06:00 DEBUG VT
> *Prepared sql query parameters : [12-24-2024
> 10:35:00,2024-12-24,0,150,2798075]*

*[image: RDS Logo]*
*Steve Kenow*
Manager, End-User Services and Support - RDS MN
<https://www.rdspos.com/Minneapolis-Minnesota-Grocery-Point-of-Sale-System>
Direct: (952) 392-2686
Office: (952) 934-4001
Email: skenow at rdspos.com

[image: Icon 1]
<https://mailtrack.io/trace/link/d5e46ac8cfdec7b8ebdc539696dd45306644b800?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FGrocery&userId=3091118&signature=18b062316c510b1b>
[image:
Icon 2]
<https://mailtrack.io/trace/link/b0fdfdd837e0d187e174cae0c9479c9b847c4e36?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FQuick-Service%2FPoint-of-Sale-Solutions&userId=3091118&signature=b26cf2b23255a2a2>
[image:
Icon 3]
<https://mailtrack.io/trace/link/9c1116af49d5de3a851b38185dbd7ba07d27def2?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FRestaurant%2FPoint-of-Sale-Solutions&userId=3091118&signature=78db9a7d4392c7ed>
[image:
Icon 4]
<https://mailtrack.io/trace/link/c5c6a63b04b163898650fb7e2fdd7312ca923cdf?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FGeneral-Retail&userId=3091118&signature=1ec7a1d9db94a0f1>
[image:
Icon 5]
<https://mailtrack.io/trace/link/9d0a121b09b0d5e1ba1c5be04c5c2b8d969b7d2c?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FConvenience-Store%2FNCR-Radiant-Convenience-Store-POS-System&userId=3091118&signature=112f29b42fe5a787>
[image:
Icon 6]
<https://mailtrack.io/trace/link/16b4ffb1c4363203009e09666cb41ce82f3a39c1?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FRDS-Payment-Services&userId=3091118&signature=84ffb1248e80fb55>
------------------------------

Support Questions/Issues? Email rdshelp at rdspos.com (non-emergencies) or
call (952) 934-4002 24/7

On Fri, Dec 20, 2024 at 3:50 PM Steve Kenow <skenow at rdspos.com> wrote:

> Thanks, Patrick.
>
> I changed the displaytype to 2 (it was 1), and the value was not changed
> when I edited the record - as desired. However, on a ticket where the value
> hadn't  been set and the status field changed to 'Closed', it wasn't
> updated by the workflow - not as desired.
>
> Changing the displaytype to 3 hid the field completely.
>
> I still have the uitype as 70, which is how the system datetime fields are
> configured. I'll test your suggestions in combination with the displaytype
> options.
>
> *[image: RDS Logo]*
> *Steve Kenow*
> Manager, End-User Services and Support - RDS MN
> <https://www.rdspos.com/Minneapolis-Minnesota-Grocery-Point-of-Sale-System>
> Direct: (952) 392-2686
> Office: (952) 934-4001
> Email: skenow at rdspos.com
>
> [image: Icon 1]
> <https://mailtrack.io/trace/link/d5e46ac8cfdec7b8ebdc539696dd45306644b800?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FGrocery&userId=3091118&signature=18b062316c510b1b> [image:
> Icon 2]
> <https://mailtrack.io/trace/link/b0fdfdd837e0d187e174cae0c9479c9b847c4e36?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FQuick-Service%2FPoint-of-Sale-Solutions&userId=3091118&signature=b26cf2b23255a2a2> [image:
> Icon 3]
> <https://mailtrack.io/trace/link/9c1116af49d5de3a851b38185dbd7ba07d27def2?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FRestaurant%2FPoint-of-Sale-Solutions&userId=3091118&signature=78db9a7d4392c7ed> [image:
> Icon 4]
> <https://mailtrack.io/trace/link/c5c6a63b04b163898650fb7e2fdd7312ca923cdf?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FGeneral-Retail&userId=3091118&signature=1ec7a1d9db94a0f1> [image:
> Icon 5]
> <https://mailtrack.io/trace/link/9d0a121b09b0d5e1ba1c5be04c5c2b8d969b7d2c?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FConvenience-Store%2FNCR-Radiant-Convenience-Store-POS-System&userId=3091118&signature=112f29b42fe5a787> [image:
> Icon 6]
> <https://mailtrack.io/trace/link/16b4ffb1c4363203009e09666cb41ce82f3a39c1?w=anNrb2xha0ByZHNwb3MuY29t&url=https%3A%2F%2Fwww.rdspos.com%2FProducts-Solutions%2FRDS-Payment-Services&userId=3091118&signature=84ffb1248e80fb55>
> ------------------------------
>
> Support Questions/Issues? Email rdshelp at rdspos.com (non-emergencies) or
> call (952) 934-4002 24/7
>
>
> On Fri, Dec 20, 2024 at 6:46 AM Alexander Allen <
> alexander.allenz at gmail.com> wrote:
>
>> Hello. I also use custom field date on Help Desk module. I found similar
>> uses as you. To fix it I set that fields to not display on edit mode (In
>> the vtiger_field table change display time from 1 to 2 or 3, don’t
>> remeber). Also I put the UITYPE as 1 and let Date time as format.
>>
>> If this also not works, change your table vtiger_ticketcf field forme
>> date time to varchar. If you this, get a backup of your table if something
>> does not work.
>>
>> I remember that the main key is to not show the field in the Edit Mode.
>>
>>
>>
>>
>> On Fri, Dec 20, 2024 at 04:37 Alan Lord <alanslists at gmail.com> wrote:
>>
>>> vtiger open source doesn't really have an "editable" datetime field
>>> UIType. The one used for Modified and Created time values is really only
>>> a read-only field type.
>>>
>>> I had to create a custom UItype field for one customer who really wanted
>>> an editable datetime field. You will also need a different UX library to
>>> let you edit it in Detail and Edit Views. FWIW I used a small library
>>> called FlatPickr. Honestly it was a right PITA and took me ages to get
>>> all the possible ways a user could edit/view it to work properly in
>>> multiple timezones.
>>>
>>>
>>> Al
>>>
>>>
>>> On 19/12/2024 23:02, Steve Kenow wrote:
>>> > Login and set calendar preferences to mm-dd-yyyy
>>> > Navigate to a closed ticket
>>> > Edit - make no changes
>>> > Save
>>> >
>>> > Result: Closed Date (cf_825) is saved as 0000-00-00 00:00:00
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>>
>> _______________________________________________
>> http://www.vtiger.com/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20241224/6d47a47e/attachment.html>