Salesforce Time Field Mismatch

I recently created a volunteer time form. I checked the time zones for both Salesforce and Jotform and they are both Eastern Standard time but when the entry transfers to Salesforce, the time is incorrect.

Please see the two top entries from April 11th. I had to manually go in and change the others.

Hi Hallie,

Thanks for reaching out to Jotform Support. I understand the issue, but I’ll need a bit of time to work out a solution. I’ll get back to you shortly.

Thanks for your patience.

Hi Hallie,

I appreciate your patience. I cloned your form and tested it to see if I could replicate the issue, but everything was working properly. Check out the screenshot below to see my results:

You can see the same time on the Salesforce object:

Since we are not able to replicate the issue it will be very difficult to suggest a solution. You can try the below troubleshooting steps:

• Separate Date and Time Fields: If you're using a combined Date and Time field, consider separating them into two distinct fields. This can sometimes resolve synchronization issues. 
• Check Date and Time Formats: Ensure that the date and time formats in Jotform match those expected by Salesforce. This includes checking AM/PM notation and 24-hour settings. 
• Re-Integrate with Salesforce: Sometimes, re-integrating your form with Salesforce can help refresh the connection and resolve any mismatches. 
• Adjust Time Zone Settings: As you've mentioned adjusting the time zones, it's crucial to ensure that both the org level and user level time zones in Salesforce are set correctly. A mismatch at the user level might cause the time to be recorded incorrectly.
• Consult the Salesforce Setup: It may be beneficial to review the Salesforce setup for any potential issues that could affect the time field. Salesforce has its own set of documentation that might provide additional insights.

Please give it a try and let us know how it goes. 

It is still not working for me and I have tried these solutions and more. I think it is likely on Salesforce's end though so I will keep trying!