In Project 2003 when we accepted task updates it automatically opened the respective schedules and then you could publish afterwards (usually automatically on save). Now in project 2007 it just adds it all into a queue. However the updates, new tasks etc. don't get published on the acceptance because the updates are all done off line. I get dozens of task updates a day and have 42 current projects. I don't want to have to open all 42 every day to republish just in case there has been an update. So is there any 'best practice' out there to make sure updates are published?
Hello Josie, Brian Smith describes one way of doing it in his blog. You can find it there: http://blogs.msdn.com/brismith/archive/2008/05/06/how-to-ensure-your-accepted-updates-get-published-in-project-server-2007.aspx We do that for many clients and it works fine. Hope it helps. Patrice "JosieMarley" wrote: > In Project 2003 when we accepted task updates it automatically opened the > respective schedules and then you could publish afterwards (usually > automatically on save). > > Now in project 2007 it just adds it all into a queue. However the updates, > new tasks etc. don't get published on the acceptance because the updates are > all done off line. > > I get dozens of task updates a day and have 42 current projects. I don't > want to have to open all 42 every day to republish just in case there has > been an update. So is there any 'best practice' out there to make sure > updates are published?
Thank you for your reply - this will really help! "PatLac" wrote: > Hello Josie, > > Brian Smith describes one way of doing it in his blog. > > You can find it there: > http://blogs.msdn.com/brismith/archive/2008/05/06/how-to-ensure-your-accepted-updates-get-published-in-project-server-2007.aspx > > We do that for many clients and it works fine. > > Hope it helps. > > Patrice > > "JosieMarley" wrote: > > > In Project 2003 when we accepted task updates it automatically opened the > > respective schedules and then you could publish afterwards (usually > > automatically on save). > > > > Now in project 2007 it just adds it all into a queue. However the updates, > > new tasks etc. don't get published on the acceptance because the updates are > > all done off line. > > > > I get dozens of task updates a day and have 42 current projects. I don't > > want to have to open all 42 every day to republish just in case there has > > been an update. So is there any 'best practice' out there to make sure > > updates are published?
