Persisting transformation expressions on datahub

[Former Member]

Hi All When we change the transformation expression of a target item, and restart datahub with kernel.autoInitMode=update. It ends up that the target item still uses the old transformation expression. Once we restart with kernel.autoInitMode=create-drop then it uses the new expression. Could it be that you persist the transformation expressions in datahub tables? Anyone facing this?

[rafal_gdowski · Accepted solution]

Yes, the transformation expressions are stored in the database.

 SELECT * FROM integration.TargetAttrDef;

The value does not get updated if it exists already.

I have not tried this, but you could set the override="true" attribute and see if that will fix your problem (although this feature was intended to truly override definitions from other extensions).

[Former Member · Accepted solution]

Thank you Rafal. I'm not aware what is the override="true". In extensions.xml? We are using 5.5.1. Appreciate your quick response as we are literally dropping our production schema tomorrow for this issue

[rafal_gdowski · Accepted solution]

In 5.5.1 that will now work. We implemented that feature starting in 5.6

[rafal_gdowski · Accepted solution]

Try updating the table instead of dropping the schema. Do the changes in both places (db & xml, so you are not 'out of synch')