When creating MA from a project ( let's say A Project), A Project is created from Project Template B.
In Project Template, we have a Description field, it's a standard field.
Problem is when creating MA from a project, the description of Project template B is carried over to description field of MA. Is there anything we can do to stop this flow of description from project template to Master agreement? it does not make sense.
Is project template description stored somewhere within the datadabase table for project? so we can reset the column as null, then master agreement won't get prepopulated with project template's description?
Much appreciated if someone can shed some light here.