I am having validation errors when moving between test and production servers. I have a package which is reading and XML file and loading the data into staging tables. The XML source is configured to use a variable for the file name (which is
getting populated through a foreach loop. The default value points to a file that was on the production server when the package was created). The XSD is stored on a network share.
This all looks fine in test. When I deploy it to production there are no validation errors, but when I run it, I get errors about the first few columns in the schema complaining:
"The external column "<Column Name>" (2639) has no mapping to the XML schema"
If I open the package while pointing to the production server, I can double click the XML Source and clear the errors. I can then redeploy it and the package will run without issue in production. However, if I open it back up and the
package is again pointing to the test server, these metadata errors come up again.
I have rebuilt this component and the XSD a dozen times, thinking that the component was corrupted, but nothing seems to help. I even rebuilt the entire dataflow. Any ideas on to make this transition from test to production more smooth?
Is there a more reliable way that I can configure t
View Complete Post