What should you avoid applying 'OMIT' on, according to best practices?

Applying 'OMIT' on key fields is discouraged because key fields are essential for accurately linking different tables in a data model. They play a critical role in establishing relationships and ensuring data integrity within the Qlik Sense application. When key fields are omitted, it can lead to incomplete or inaccurate data associations, which negatively impacts the overall effectiveness of the data model. This disruption can compromise analytical capabilities and lead to erroneous insights derived from the data.

In contrast, descriptive fields, numeric values, and text fields may not have the same level of importance in terms of linking tables and may be handled differently in the context of data cleaning or preparation without jeopardizing the relational structure of the data model. Therefore, it is best practice to be cautious when applying 'OMIT' to key fields to maintain the robustness and reliability of the data architecture.