"Out of synchronization" warning for column that is not mapped
Posted: Fri 16 Sep 2016 15:20
Recently, the width of a column in Salesforce was changed. The Salesforce Destination Component then warned of that column being "out of synchronization". The column is not mapped.
Why is the component tracking un-mapped columns? One of the features of Salesforce is that columns can be easily added. Will I have to be constantly monitoring all components because of possible unrelated changes?
Resolving the issue requires that I hunt down the differences (over time, there could be many) and make the required changes in the advanced editor. If a changed column is mapped, this is acceptable and expected.
Refreshing the component is not an acceptable solution. With the large number of column involved, re-mapping is tedious and error-prone and it is a serious software change that would require that the project go through full QA again, for basically no reason.
Yes, it is a warning and (probably) does not impact operation. However, the component only displays one warning at a time. I cannot ignore a warning that is for a column that is not mapped because how do I know that there is not a second warning waiting behind it that does involve a mapped column?
This useless and unwarranted dependency is no different than if someone on the other side of the world turns on a particular light switch which requires you to go around your house and flush all the toilets.
Regards,
John
Devart SSIS Data Flow Components v1.5.283 (Salesforce)
Why is the component tracking un-mapped columns? One of the features of Salesforce is that columns can be easily added. Will I have to be constantly monitoring all components because of possible unrelated changes?
Resolving the issue requires that I hunt down the differences (over time, there could be many) and make the required changes in the advanced editor. If a changed column is mapped, this is acceptable and expected.
Refreshing the component is not an acceptable solution. With the large number of column involved, re-mapping is tedious and error-prone and it is a serious software change that would require that the project go through full QA again, for basically no reason.
Yes, it is a warning and (probably) does not impact operation. However, the component only displays one warning at a time. I cannot ignore a warning that is for a column that is not mapped because how do I know that there is not a second warning waiting behind it that does involve a mapped column?
This useless and unwarranted dependency is no different than if someone on the other side of the world turns on a particular light switch which requires you to go around your house and flush all the toilets.
Regards,
John
Devart SSIS Data Flow Components v1.5.283 (Salesforce)