Just upgraded our production CRM to 7.10.16. On the Home Page, in each of the Dashlets, if there is a due date variable in the list view (doesn’t matter if the dashlet is tasks, calls, etc.) the information displayed for the record is actually the value of the start date.
For example: I have a task with a start date of 06/03/2019 and the due date is 06/17/2019. On the record’s detail view, this is correct. If I look at “my open tasks” on the home page, it says the due date is 06/03/2019.
Where could I go to look at the dashlets so I could determine why it is passing the wrong data?
If I remove the Due Date field from the dashlet and readd it, the date pulls in correctly. However, if you log out and relogin/clear web cache and history the due date reverts back to displaying the start date.
No still can’t find what is going on. I tried to go to dashletdefs hoping somehow the start date variable got paired with the end date label or something, but alas nothing. I didn’t notice it until production because I don’t use dashlets very much and it wasn’t a primary concern of what was being updated. After going back to my older implementations that I was using for development, I realized this problem has been occurring all along on each build. I’m guessing it is some sort of javascript or caching issue because as I stated earlier, I can get it to display everything correctly if I try to edit the individual dashlet and then save it (so it refetches the task data) but as soon as you log out and log back in the end dates have reverted to displaying the start date value.