https://community.qlik.com/t5/Catalog-and-Lineage/schema-evolution/m-p/1765241#M520 <P>Hi, in the single box installation there is no option for adding the new field.</P><P>What are your best practices and workarounds for this kind of problems with schema evolution? I assume that my entities will have a data types changed, columns removed and added.</P><P>One option might be to remove old entity and add the new one, but it will affect:</P><P>-lineage</P><P>-publishing jobs</P><P>-dataflows</P><P>-statistics</P><P>-historical loads.</P><P>what is your approach to deal with schema evolution?</P><P>best regards, rd</P> Tue, 07 Dec 2021 22:26:21 GMT pandabrowski 2021-12-07T22:26:21Z https://community.qlik.com/t5/Catalog-and-Lineage/schema-evolution/m-p/1765241#M520 <P>Hi, in the single box installation there is no option for adding the new field.</P><P>What are your best practices and workarounds for this kind of problems with schema evolution? I assume that my entities will have a data types changed, columns removed and added.</P><P>One option might be to remove old entity and add the new one, but it will affect:</P><P>-lineage</P><P>-publishing jobs</P><P>-dataflows</P><P>-statistics</P><P>-historical loads.</P><P>what is your approach to deal with schema evolution?</P><P>best regards, rd</P> Tue, 07 Dec 2021 22:26:21 GMT https://community.qlik.com/t5/Catalog-and-Lineage/schema-evolution/m-p/1765241#M520 pandabrowski 2021-12-07T22:26:21Z