Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
Action-Packed Learning Awaits! QlikWorld 2023. April 17 - 20 in Las Vegas: REGISTER NOW

Source Properties when Inherited to Entity, should be Visible in Entity Level Properties

cuttsdl
Contributor III
Contributor III

Source Properties when Inherited to Entity, should be Visible in Entity Level Properties

This Property that can be set at Source:  default.field.allow.non.ascii.chars.  It gets inherited to the Entities associated with it.  However, when you look at the Entity Property, it's not displayed that it's been applied.  There's no Qlik documentation that lists which properties are inherited without drilling into each one in their documentation to understand if it's inherited or not

Qlik documentation for the Property noted above:  Boolean controlling whether or not non 7-bit ASCII chars are allowed in fields.  Set this at the entity or source level if you expect your content to contain international characters or extended punctuation characters. By default, The application only allows 7-bit US-ASCII characters … US English only. This is the case even if your specified CharEncoding supports other characters. Examples are EBCDIC_037, LATIN_1, and WINDOWS_1252 which support accented Latin characters. All Unicode encodings (UTF_8, UTF_16LE, UTF_16BE, UF_32LE, UTF_32BE) support all major modern languages.

Two issues. 

1. Visibility to all Properties assigned at each level.

2. Having this information easily provided in documentation could save time in advertently adding it at lower level, when it could have been entered at a higher level once.

 

 

Tags (3)