[Bug] Adding columns messes joins

When you make a change to the object you have update all downstream objects as well.
In some cases  all you need to is to open the object and click OK.

This is done and intentionally and we will keep as it is.
Because you as user have to understand what happened to the data and make a conscious decision about it.

Here is an example.

Let assume that you are loading financial data in the following format.

Data
Account
Money In
Money Out

Everything is working as expected

Now if we insert  a new field called Description after Account filed and
there were no warning, no need to update mapping or check the mapping

"Money In" field may go into "Money Out" = you lost all your monies.

 

admin wrote:

When you make a change to the object you have update all downstream objects as well.
In some cases  all you need to is to open the object and click OK.
 

Just opening doesn't resolve it , I believe opening , disconnecting and reconnecting does the trick, which should be fine. 

I agree with logic, this is why ensure that for all critical transformations , I ensure a field reorder before them just to make sure new objects are always added at the bottom.