I was trying out the automation function to link important dates from several project plans to one central location that will act as a calendar.
Automation is: If "Add to calendar" = checked, copy row to calendar sheet.
The premise works well, but in cases where the date changes on the primary sheet, this does not update the row that was fed to the calendar initially.
The workaround is to ask that when a row is updated that has been shared to the calendar, that the user saves the date, then unchecks and checks the "Add to calendar" box, and saves again. This adds a new row to the calendar sheet (again, not a massive issue just takes some managing), but if the person is using predecessors or dependencies, they may miss the date changing and forget to do the workaround.
Is there something i am missing on this, that maybe can update the rows downstream when updated on the feeder sheet?
When a row is copied (or moved) to another sheet, any changes made to the original row will not reflect in the copied row unless the cells have been linked.
Since you're looking to show rows from multiple sheets in Calendar View, I would recommend creating a Report and then viewing the Report in Calendar View. When you're building your report, you could use the "add to calendar" column as the criteria that pulls rows into the report. For example, the "What" criteria in the Report Builder could be "add to calendar is checked".
When a row is copied (or moved) to another sheet, any changes made to the original row will not reflect in the copied row unless the cells have been linked.
Since you're looking to show rows from multiple sheets in Calendar View, I would recommend creating a Report and then viewing the Report in Calendar View. When you're building your report, you could use the "add to calendar" column as the criteria that pulls rows into the report. For example, the "What" criteria in the Report Builder could be "add to calendar is checked".