I am creating a master schedule with detailed project schedules as its subprojects. Everytime I change dates in the master, MS Project assigns a “start no later than” constraint in the detailed project schedule. I am looking for a way around this as I don’t my detailed project schedules to be riddled with constraints everytime I make changes to the master. Any suggestions is much appreciated. Thanks in advance.
Hi Sudhakar, that does not sound right! But where is this constraint being assigned? I’ve never seen that happen before, and I’ve used master plans since 2013, and I am currently on MSP 2016 Pro.
I agree with Jigs. Another thought, if you are changing a sub-project task in your master project, you are actually changing the sub-project. Setting a start date directly will always set a Start no earlier than constraint. That’s how Project knows to keep the task on that date.
The best way to work with a master schedule that has subprojects is by buying an add-in to manage these cross-project dependencies. At ProjectPro, we have developed an add-in, called CrossLinksPro, that can handle many hundreds (even thousands) of cross-project links, which is too hard to do with Microsoft Project by itself. Please, send me an email at EricU AT ProjectProCorp.com if you would like to see a demo or you can go to: https://projectprocorp.com/collections/software/products/crosslinkspro
There are other tools available as well from companies like Campana & Schott in Europe or Matan in Israel. I encourage you to explore them!
Hope this helps!