Best Of
Re: Analyzer Double Click to Add Dimensions/Measures
Or a shift-click functionality that allows you to select multiple columns and drag them all at the same time
Re: Make 1st letter of a field value uppercase in ETL
CONCAT(UPPER(LEFT(`YourField`,1)), SUBSTRING(`YourField`, 2))
Re: Adding and Removing Users from Datasets in Workflows
You should use the dataset id and user id in your workflow. A group id can be assigned to a dataset, but use caution using a workflow to assign a group, especially if a function is expecting a user id.
Snowflake retiring single-factor password authentication in Nov 2025
Snowflake has announced it will block single-factor password authentication by Nov 2025. ( ). This effectively means that connectors that require only username and password will no longer be able to connect to Snowflake starting Nov 2025. Customers who wish to connect their Snowflake data to Domo will need to use a connection strategy that supports OAuth or Key Pair authentication.
What does this mean for customers?
Customers using the Snowflake connectors will need to migrate to a connection strategy that either uses OAuth or Key Pair authentication. There are currently 2 options:
- If a customer is on Consumption, they can take advantage of Cloud Amplifier (CA) for Snowflake. CA supports both OAuth and Key Pair authentication, as well as write capabilities.
- Domo has OAuth and Key Pair versions of the connectors that use username and password. If a customer is not on Consumption, or they are on Consumption but are not ready to move to CA, they can use the appropriate OAuth or Key Pair version of the connector. A mapping of the connectors that require username and password, and their OAuth and/or Key Pair alternatives is at the bottom of this post.
Can Domo help customers with the migration to a different version of the connector?
Domo can migrate datasets from a connector using the username password version to the corresponding OAuth or Key Pair version. We cannot migrate datasets from one version to another that is not an OAuth or Key Pair version of the original connector. E.g, we cannot migrate customers from the standard connector to an unload connector.
How is Domo communicating this information to customers?
Domo will communicate this update as follows:
- All Knowledge Base (KB) articles will be updated to say that the username/password connectors are deprecated as of April 15th 2025. This is to prevent further power ups on the username/password connectors. The KB articles will direct users to use CA, or the OAuth/Key-Pair alternative.
- Datasets using the username/password connectors will still run, however Domo will try to prevent new power ups using these connectors as of April 15th 2025.
- An email message will be sent to affected dataset owners. The email will include the connection options above, and instructions on how to migrate their datasets to a different connector if they wish to.
Mapping of username/password connectors to OAuth/Key Pair connectors.
Username/Password version | OAuth Version | Key Pair Version |
|---|---|---|
Snowflake | Snowflake OAuth SnowflakeEnterprise OAuth | Snowflake Key Pair |
Snowflake Unload | Snowflake OAuth Unload | Snowflake Key Pair Unload |
Snowflake Unload v2 | Snowflake OAuth Unload v2 (coming soon) | Snowflake Key Pair Unload v2 |
Snowflake Managed Unload | Snowflake OAuth Internal Unload v2 Connector | Snowflake Key Pair Internal Managed Unload |
Snowflake High Bandwidth With Advanced Partitions | Snowflake OAuth High Bandwidth With Advanced Partitions | Snowflake Key Pair High Bandwidth With Advanced Partitions (coming soon) |
Snowflake Partition Connector | Snowflake OAuth High Bandwidth With Advanced Partitions | Snowflake Key Pair Partition Connector |
Snowflake Writeback | Snowflake OAuth Writeback | Snowflake Key Pair Writeback. |
Tasleema
Re: Comment out tiles in MagicETL
Commenting to bump this and hope that it gets renewed interest. @AndreaHenderson now that we have sections, the ability to comment those out and/or hide them would be awesome.
Re: How can I set up a text box Variable that can search for a text string in a field?
For the original question, I have done something like this using a BeastMode as a card filter for every card on the page, filtering for 'Include':
CASE
WHEN Text_Variable IS NULL THEN 'Include'
WHEN Text_Variable = 'Default Text' THEN 'Include'
WHEN LOWER(Description) LIKE CONCAT('%', LOWER(Text_Variable), '%' ) then 'Include'
ELSE 'Exclude'
END
I set conditions for the Control variable either being null or for whatever default text I have set for that control variable so that it only filters the data after someone has entered something into it.
Re: Removing Duplicates with Condition
You can take the minimum value of your Haz / Non-Haz text in your rank and window to determine if had any Hazardous.
Alternatively, you can use a case statement to return 1 if the value is hazardous and 0 if it's not and then take the max of that value in your case statement and then convert it back to a text value using another formula tile.
Re: Cumulative Sum for the Year on a table card
This was so close to what I had. Thank you
Re: Cumulative Sum for the Year on a table card
Hi @zaclingen_fwm,
You can do this with a window function:
SUM(SUM(`Monthly $`)) OVER (PARTITION BY `year` ORDER BY `month number` )
