grichards

i consider this a bug, wondering if anyone else sees it this way.

after creating a couple projects i went back to my setup and added some new phases. The new phases are not available in projects created prior to the addition of the phase. I can create a product, assign it to the new phase, and add the product into the older project, but the new phase info is just left out. I can try "updating from the master table", but no phase info. Basically, my new phase is just not available in the old project.

Is the philosophy that you have to be completely setup (a.k.a. im not able to adapt as i go) before integrating d-tools into my workflow? Or i have to rebuild the entire project if i decide to switch a couple gears in setup?

More than anything, this seems like a hiccup in database design. For example, if i add a phase (or any data) to my database, then all projects (read as database tables) should be able to access that data. instead it appears that a copy of the data is created for each project and is set in stone for the life of the project. Redundancy? Inconsistency?

Thoughts?

RandyB

The problem is that not all projects include all phases. You just have to add the newly defined phase to the project as follows:

1. Open the project
2. Go to D-Tools > Options > Phases
3. Click on "Add Phase"
4. You should see the new phase in the "Add Phase(s) to Project" list. Select the checkbox next to the phase and click the Add button.
5. Click Close to close this dialog.

The new phase is now available in this project. You may have to update those products already added.