Problem using Post Load Action (Combine Categories) with data from Snowflake
A user reported that they were in the process of rebuilding a system from a new ODS (Organisation Data Source) within Snowflake. The data contained 3 separate ID variables together with descriptions and the user was aiming to merge these as a hierarchy, grouping the separate levels of ID into a single table.
This previewed and ran correctly in the Snowflake GUI and produced the result as required:
However when run as a Post Load Action within Designer the query errored:
The issue was that the Snowflake ADO.Net provider does not search for column names in a case insensitive manner (as the SQL Server ADO.Net provider does).
To fix the issue we had to surround the column names in the query with double-quote characters so that Designer could find the columns:
i.e. SELECT CODE as "Code",SUMMARYCODE as "SummaryCode", SUMMARYDESC AS "SummaryDescription""
This resolved the issue. The issue will be corrected within in the Q3 2024 version of Designer but would currently affect versions prior to this.
Related Articles
Limits issue within FastStats
We’ve found and fixed an issue with the query component, where in rare situations we didn’t fully clear the limit properties between queries. This could cause a query limit clause to be mistakenly applied to a subsequent query. To apply this fix: ...Combining Table Results in Orbit using a CubeLookup Expression
Sometimes it is useful to be able to get results from a Table in Orbit and use them in another Table. Within Orbit, it isn't currently possible to refer to results in one tile within another one. However, we can use a combination of some powerful ...Add a Portion of an Array Variable in a Data Grid
When adding an array variable onto a data grid it will give you all of the options in the array. What if you were only interested in a portion of the array variable. I'll be using this variable Newspapers in this example from our holidays database. ...Issue with Environmental Variables within URLS in Designer build prior to Q2 2024
A user reported an issue within the post-load action in Designer when upgrading their system from Q1 2023 to Q1 2024. The issue occurred where an environment variable name was included within a pathname of a post-load action. Designer was reporting ...Expression Index Geo Nearest
An issue arose when a selection was created from an Geo Nearest Expression using an index. The problem was that the place was not corresponding to the coordinates on the map Visualisation. E.g. When choosing Warwick in the list on the selection and ...