SSIS package fails when Configuration value has value saved into the package

Question

when a package is migrated from dev to QA and to PROD sometimes it fails since the variables have values in them saved into the package.
what we do is clear these values manually and restart the job.
Is there a way we can clear the variables when saving the package or at least programmatically?
eddy.a

Answer 1

Hello Arthur
Thank you for your response. I should start by apologizing by not making myself clear. We do use indirect configuration that work cross environments however this is the issue that we have:
when the package is first created say you create a DB Variable called A and you enter value A in the variable to test the package. After the package development is tested, you change the configuration values to fetch data whether from an excel file or from
an XML.
when you run on environment A the package runs fine however when you move over to environment B it seems that first it validates against A then overwrites B - if environment A is not there anymore the package sometimes fails.
we are changing these manually for now but I was wondering if there's a way to prevent it.
thanks
eddy.a