It sounds like you're encountering an issue related to time zone handling when uploading events into Dynamics 365. The error you're seeing, "You must set a time zone", typically occurs when a time zone is not properly specified in the event record, or the time zone format is incorrect.
Here are the steps to troubleshoot and resolve this issue:
1. Verify the Time Zone Format
Dynamics 365 expects the time zone to be in a specific format. If you've added a time zone column to your data, ensure that the format aligns with what Dynamics 365 expects. The most common formats are:
Time Zone Name (e.g., "UTC", "Pacific Standard Time")
Time Zone GUID (which corresponds to a specific time zone record in the system)
To ensure the correct time zone format:
Time Zone Name: You can find the exact name in Dynamics 365 by navigating to Settings > Administration > System Settings > Time Zone or use the TimeZonePicker in the UI to get the correct value.
Time Zone GUID: If you are working with GUIDs, you can look up the corresponding time zone record using the Web API or fetch the time zone information directly from the system.
2. Ensure Time Zone Field is Correctly Mapped
Make sure the column for Time Zone in your data is mapped correctly to the relevant field in Dynamics 365 during the import. This includes:
Start Date/Time and End Date/Time fields should be correctly mapped to the respective event fields.
You may also need to ensure the Time Zone field is properly included as a parameter during the data import process.
3. Check for Plugin or Custom Workflow Issues
Since you've mentioned a plugin causing the issue, it's worth investigating whether it's interfering with the event data upload. If you're unable to disable the plugin directly, try the following:
Review the Plugin Trace Logs: If you have access to plugin trace logs in Dynamics 365, they can provide more detailed information about which part of the plugin is causing the issue.
Temporarily Disable or Unregister the Plugin: If you are certain the plugin might be the root cause but you cannot disable it from the UI, you can use the Plugin Registration Tool in the XrmToolBox or the Developer Resources section to unregister the plugin. Before doing this, make sure you take a backup of your plugin configurations.
If you're not 100% sure that the plugin is causing the issue, I recommend reviewing the specific actions that the plugin takes and try isolating the problem by performing the import while keeping the plugin active for other entities or records.
4. Validate the Import Data
Double-check your event data for any discrepancies that might cause the error:
Ensure the Time Zone Field Is Populated: Check that the time zone field is correctly filled for each record, and no empty or invalid values are being passed.
Format Date and Time Properly: Ensure that your start and end date and time fields are formatted according to Dynamics 365 requirements (e.g., MM/DD/YYYY HH:MM AM/PM in the system time zone format).
5. Test with a Single Event Record
As a quick test, try uploading a single event record with properly populated date, time, and time zone fields. This can help identify whether the issue is with the data format, the plugin, or the broader import process.
6. Use Power Automate or API as an Alternative
If the plugin is still a concern, you can bypass it temporarily by uploading events using Power Automate or the Dynamics 365 Web API. This allows for more control over the data import process, including how the time zone is handled.