When you manually update a schedule item via the editor and publish changes, the information (including any date/time changes) is automatically reflected in the My Schedule section of any user who has added those items to their My Schedule.
When it comes replacing a schedule via CSV import, however, things are a little trickier. This is because its hard for us to know what items are updates versus deletions versus new items.
So here's how it works:
When handling imports that are replacing schedule data, we keep stability for items that are completely identical -- so those items will not be affected in My Schedule.
For any items that are not exact matches, though, we treat them as new, and we delete items not included in the new import. This can have the (possibly unintended) effect of removing items from users' My Schedule lists.
Using Unique ID to Ensure Accurate Updates
To make sure updates to your schedule are properly reflected in users’ My Schedule:
Include a Unique ID column in your CSV file when importing or updating schedule items.
Each row should have a consistent Unique ID that doesn’t change between imports.
When you import a file with Unique IDs that match existing events, Yapp knows which events to update, and users' My Schedule will be updated accordingly.
Here’s a simple example of a CSV file that includes a Unique ID column for use with the Schedule or Multi-Track Schedule in Yapp:
Unique ID | Title | Date | Start Time | Description |
session-001 | Opening Keynote | 06/10/2025 | 9:00 AM | Join us to kick off the event with our keynote speaker. |
session-002 | Workshop: Product Design | 06/10/2025 | 10:30 AM | A hands-on session focused on user-centered design practices. |
session-003 | Networking Lunch | 06/10/2025 | 12:00 PM | A casual networking opportunity over lunch. |
session-004 | Panel: Future of Tech | 06/10/2025 | 2:00 PM | Industry leaders discuss emerging trends. |