Hi there,
I am running into this over and over again, so I finally decided to post in the forum about it.
Whenever there's a schema mismatch, clicking OK on the Check Tables Schema dialog saves the underlying job XML but eventually leaves it in a corrupted state, forcing you to recreate the job file. Here's a common scenario.
1. I have two sites: dev and production
2. On dev I create a job that imports from an XML file into EcomProducts. This job copies into a new product field I added in dev.
3. When done, I copy the job to production. I forgot to add the custom field in production.
4. Opening the job leads to a schema mismatch warning which is expected. I click the green checkmark Check Tables Schema which highlights the issue.
Clicking OK to close the dialog corrupts the job,. At first site, there's no issue. My list of columns is loaded and the column that was not added to production shows up as None. That's fine. I then move away from the job (confirming I am OK with losing my changes (which I won't as it turns out) to add the field to the Product Fields section. When I come back to the job, all mappings are gone. There's no table or column mapping anymore.
Notice I didn't click Save or Save and close. All I did was clicking OK on the Check Tables Schema dialog which apparently saves the job internally. I think that's bad for two reasons:
1. There's no escape; closing the dialog means you're screwed
2. It corrupts the job, forcing you to fully recreate it.
Anyone else seeing this?
Happy to provide more information and repro steps if needed.
Cheers,
Imar
