ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Constraints behavior in MSP when using a template


Article ID: 196109


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


How do constraints behave when using constraints in MSP?

See the scenario below:

The template has mixed constraint types. "As Late As Possible" type did not get carried to the new project created from the template. All "As Late As Possible" constraints changed to "As Soon As Possible."


Release: All

Component: Microsoft Project Interface


In Clarity, there are only the following constraints:

These do not include the 'As Late as Possible' constraint that the end-user uses in the MSP project template (this constraint is only in MSP). When the end-user creates a project from a template, it cannot copy constraint values that do not exist in Clarity. So since the tasks do not have any of the six constraints on the screenshot (in the introduction field), when the end-user creates a project from a template, the new project will have no constraint for the tasks. When a new task has no constraint and is exported to MSP, MSP assigns it the default constraint of 'As Soon as Possible.' This behavior happens because the end-user is using a constraint that exists only in MSP. When the end-users copy a project from a template, none of the MSP specific values copy over.