Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Suggest an Idea

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

Compose for Data Warehouse should support varchar(nomax) and nvarchar(nomax) on source database

Stewart_Harding
Contributor II
Contributor II

Compose for Data Warehouse should support varchar(nomax) and nvarchar(nomax) on source database

Often data is being delivered and stored as JSON. Typically the source database will use varchar or nvarchar(nomax) to hold the JSON text. We need compose to be able to present such attributes for mapping into our data warehouses. 

The mapping will typically use the JSON functions but this can't be done unless the attribute from the source database is displayed for mapping.

In current versions of compose attributes of NOMAX are simply ignored and are not presented on the mapping interface.

Tags (1)
1 Comment
TimGarrod
Employee
Employee

Hello, the current method to support MAX / NOMAX attributes is to leverage a view that performs the parsing of the data (or a query based process). 

If you are on Snowflake, please note that VARIANT data types are supported for storing data and for mapping of these JSON structures.

Status changed to: Closed - Declined