https://community.qlik.com/t5/Suggest-an-Idea/Compose-for-Data-Warehouse-should-support-varchar-nomax-and/idi-p/1956480 <P>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.&nbsp;</P> <P>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.</P> <P>In current versions of compose attributes of NOMAX are simply ignored and are not presented on the mapping interface.</P> Fri, 15 Jul 2022 13:30:24 GMT Stewart_Harding 2022-07-15T13:30:24Z https://community.qlik.com/t5/Suggest-an-Idea/Compose-for-Data-Warehouse-should-support-varchar-nomax-and/idc-p/2020870#M11527 <P>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).&nbsp;</P><P>If you are on Snowflake, please note that VARIANT data types are supported for storing data and for mapping of these JSON structures.</P> Fri, 30 Dec 2022 16:25:09 GMT https://community.qlik.com/t5/Suggest-an-Idea/Compose-for-Data-Warehouse-should-support-varchar-nomax-and/idc-p/2020870#M11527 TimGarrod 2022-12-30T16:25:09Z