My workaround for now was to create a process builder that uses a custom date field(Meeting_Date__c) as the entry point and then convert that date field to datetime based off of the user’s current time zone.
For anyone that is curious:
- User formula field to capture the user’s timezone: (VALUE(MID(Time_Zone__c, 5, 3))) * (-1) / 24
- Process builder conversion to convert custom date field to datetime at 12:00AM: DATETIMEVALUE([Event].Meeting_Date__c )+(($User.User_Timezone_Conversion__c )+0.04167)
