Is there a way to do this in Microsoft Project Online? Additionally, is there a way to include a task in two projects (online) that is NOT a dependency? I just have the same singular task affecting two separate projects (two separate teams need to see it is complete). I have Googled and Googled and I can't find anything but desktop answers. Help!?
So - while this is a lifesaver that I thank you for - it only fixes half of my "issue". The question is - could you still link the tasks if, say, the name of CAR 3 changes every week? Like say - 3 is the number of the current week; so next week it becomes CAR 4 and so on, until CAR 53. Is there a solution for that? Like maybe some VBA code or something like that that I could use? Thank you very much!
The challenge is project links by line # and not UID and as you know, task positions w/in the schedule can change which is why using the UID as much as possible is the most desired way to work w/in the task dependencies and reporting. So if you add a task between lines 5 and 6 and you have an external link from another schedule to line 6, now that other schedule reflects the NEW task data and not what you had originally intended because the NEW task is now line 6 and the OLD line 6 is the NEW line 7. I had to deal w/ this and we found a work around. It created some more work and diligence on our part, but it worked for us. I don't know if our situation would match yours though. What we did was to keep a generic schedule which was our "live" schedule and linked and a few other schedules to a higher level master schedule so all the minor schedules fed to the major one. When we had to update, we updated the live schedule and then for the weekly stuff we would save the live schedule and add the date at the end of the file name and then post it on share point for everyone to access at the end of the week. Kept everyone on track and also archived our weekly updates so we could go back and look at any history we needed to. It wasn't perfect but it what we needed it to do which was track everything together. inadvertently
Exactly what I was looking for, cheers.
Thank you!
Thanks!
Thank you
God bless you
Exactly
❤
Is there a way to do this in Microsoft Project Online? Additionally, is there a way to include a task in two projects (online) that is NOT a dependency? I just have the same singular task affecting two separate projects (two separate teams need to see it is complete). I have Googled and Googled and I can't find anything but desktop answers. Help!?
So - while this is a lifesaver that I thank you for - it only fixes half of my "issue". The question is - could you still link the tasks if, say, the name of CAR 3 changes every week? Like say - 3 is the number of the current week; so next week it becomes CAR 4 and so on, until CAR 53. Is there a solution for that? Like maybe some VBA code or something like that that I could use? Thank you very much!
The challenge is project links by line # and not UID and as you know, task positions w/in the schedule can change which is why using the UID as much as possible is the most desired way to work w/in the task dependencies and reporting. So if you add a task between lines 5 and 6 and you have an external link from another schedule to line 6, now that other schedule reflects the NEW task data and not what you had originally intended because the NEW task is now line 6 and the OLD line 6 is the NEW line 7.
I had to deal w/ this and we found a work around. It created some more work and diligence on our part, but it worked for us. I don't know if our situation would match yours though. What we did was to keep a generic schedule which was our "live" schedule and linked and a few other schedules to a higher level master schedule so all the minor schedules fed to the major one. When we had to update, we updated the live schedule and then for the weekly stuff we would save the live schedule and add the date at the end of the file name and then post it on share point for everyone to access at the end of the week. Kept everyone on track and also archived our weekly updates so we could go back and look at any history we needed to. It wasn't perfect but it what we needed it to do which was track everything together.
inadvertently