Juan1
7 July 2024 20:08
1
Hello, IĀ“m using version 8.6.1 and I want to create a field āDateā for contacts.
My config is set to dd-mm-yyyy, but the system uses mm-dd-yyyy when I deploy. Is there a way to change it?
Also, I cannot fo back before 2014. Is there a way to expand this? I attached the image of my problem.
Many thanks!
Check your Profile / Advanced / Locale / Date Format
.
Juan1
8 July 2024 00:05
3
Thanks @chris001 , this is what I mentioned. The Date format in my profile has already been changed, but somehow in contacts, it is not using the same:
Could you check this issue, is it the same as what you are experiencing?
opened 10:38AM - 06 Apr 22 UTC
closed 12:51PM - 03 Feb 23 UTC
Type: Bug
Priority:Important
#### Issue
In Safari browser the DatePipe conversion fails and causes the vā¦ iew to not render appropriately. This can be reproduced in any SCRM ListView that displays the createdAt timestamp column.
#### Expected Behavior
DatePipe conversions being done with `date:getDateTimeFormat()` should work without throwing errors in Safari, to prevent render issues.
#### Actual Behavior
- In ListView components the content of the table rows is only rendered partially or not at all (blank table cells)
- browsers web development console shows occurrence of frontend errors from DatePipe conversions
#### Possible Fix
I am not proposing a fix for the root issue here. Only a fix to illustrate that the Safari render issues can be fixed by fixing the Date formatting issue.
When you change `{{field.value | date:getDateTimeFormat()}}` to `{{field.value}}` in file
`crm/core/app/core/src/lib/fields/datetime/templates/detail/datetime.component.html`
the ListView records are displayed correctly (but of course with unformatted dates)
#### Steps to Reproduce
1. Open https://suite8demo.suiteondemand.com/#/email-templates in Safari browser
2. Make sure the records creation date column is visible in the ListView
![image](https://user-images.githubusercontent.com/1623552/161952289-4152b8b7-747b-4ee9-8b73-031e490e1b66.png)
#### Context
Seems to only affect Safari browsers - we did not experienced date conversion issues in Chrome/Firefox.
It probably affects all views where this date conversion is being used `date:getDateTimeFormat()`.
#### Your Environment
* SuiteCRM Version used: 8.0.4, 8.1.0
* Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Safari 14.1.2 (16611.3.10.1.6)
* Environment name and version (e.g. MySQL, PHP 7): PHP 7.4
* Operating System and version (e.g Ubuntu 16.04): macOS 11.5.2
Juan1
8 July 2024 14:55
5
No @chris001 , unfortunately, itĀ“s not the same issue. IĀ“m using Chrome, not Safari, and the problem is not a rendering problem but a configuration problem (I tried the console and no errors showing). Also tried changing the file with no difference.
I believe something is overwriting the date format as it is configured dd/mm/yyyy in the user profile, as the form is showing mm/dd/yyyy but canĀ“t find it.
Thanks for all the help!
It looks like you have set date format to mm/dd/yyyy in the profile.
1 Like
Juan1
8 July 2024 15:39
7
Glad that you found a solution!
Please click āSolutionā under your reply containing the solution to your issue, as this will help other users find it faster!
Juan1
8 July 2024 17:47
10
Sure, many thanks everyone!
Juan1
8 July 2024 18:20
12
Sorry, IĀ“m new to this. Yes, that was the solution. I already adjust it.