Forums

CRM DateTime Issue - Birthday Cancel The title field is required!

1. Missing user

   
   16 Jan 2017

   Link to this post

   Hey guys,
   
   I was wondering if any of you have ran into an issue with some date formatting on the portal. In CRM, the Birthday field specifically, it is saved as a Date-Only field and always has the time set to 12:00AM. When displaying on the portal it is always a day behind. I'm thinking this is due to the portal assuming it's UTC and formatting it back to local, which would be 12:00AM - 7 hours (MST) to make it the day previous.
   
   I've tried setting the Hour Override attribute on the widget to be 12 (add 12 hours) but it doesn't even seem to be submitting with the correct format.
   
   Is there something easy I can do to resolve this or do I have to write javascript to add 12 hours to the date so it displays correctly?
   
   Thanks.
   
   Matt
2. Clinton Bale

   

   126 posts
   Registered:
   21 Feb 2014
   20 Jan 2017 in reply to Missing user

   Link to this post

   Hi Matt,
   
   We've also noticed this issue with the DateTime widget when it is specifically set to use the Birthday field. This is in our issue list and is in queue to be fixed.
   
   Other DateTime fields that use the ​date only setting do not reproduce this behaviour, so we're thinking it has something to do with the birthday as a built-in system field.
   
   I will keep you informed of our progress on this issue.
   
   Regards,
   Clinton
3. Missing user

   
   18 Sep 2019

   Link to this post

   Hi guys,
   
   Any fix for this issue? We are having the same issue when trying to set birthday for users. In CRM the field is set as Date only, but when updated through the portal we get the previous day being set.
   
   Regards,
   Virgil
4. Josh

   

   47 posts
   Registered:
   01 Jun 2018
   Answered

   30 Oct 2019 in reply to Missing user

   Link to this post

   Hello Virgil,
   
   Thank you very much for reaching out to us regarding this issue. We have identified the problem and released a solution in The Portal Connector 5.2 (minor revision 108). This fix will also be included in the next minor release of The Portal Connector 5.1 (minor revision 143). You should no longer experience this issue upon upgrading to one of the versions mentioned.
   
   If you have any other questions or this issue persists after upgrading, please feel free to reply to this thread, or for more complex issues you can email support@crmportalconnector.com.
   
   Cheers,
   
   Josh