Best Of
Re: Business in a Box Access
It's a feature switch. Talk to your CSM or email support@domo.com
Re: Snapshotting Data
You can also use the Dataset Copy connector [https://domohelp.domo.com/hc/en-us/articles/360043436533-DataSet-Copy-DataSet-Connector] to create a snapshot (with the update setting being Append).
amehdad
Re: Snapshotting Data
Hi @JackMcG, have you read through these knowledge articles:
Magic ETL 1.0: Creating a Recursive/Snapshot Magic ETL DataFlow
Magic ETL 2.0: Creating a Recursive/Snapshot DataFlow in Magic ETL v2 (Beta)
amehdad
Re: 3+ Consecutive days
the problem with window functions in analyzer in this context is that you MUST show date on the axis in order for the lag function to work.
I assume you'd only want to show rows if there were 3 consecutive days of xyz status.
if my assumption is correct, you'd want to implement your lag calc in ETL so that you have a column to work with as @MarkSnodgrass suggests.
you may want to implement lag(date, 1) , lag(date, 2), lag(date, 3) and add them as columns. From there you could use datediff functions in beast mode to decide whether to display the columns or not.
Re: Bulk Credential Changes
This seems like a pretty significant business continuity issue. The only way around it I can think of would be to create a dummy Domo user dedicated to owning these dataset accounts, but that's not ideal if you have limited licenses.
Re: Cloud connector or Workbench to get data into instance.?
@Tsharma8724, I would add that a few scenarios for using workbench could be:
- Accessing a siloed amount of data, relevant to you and your region/teams, from a platform that is managed by global headquarters.
- If your business deals with some highly sensitive data then having a local network point of ingestion is a more secure option, than a potentially more exposed route of web UI connectors, to get your data.
amehdad
Re: Cloud connector or Workbench to get data into instance.?
Hi @Tsharma8724
The main difference is from a security standpoint. The cloud connector will have Domo connect directly to your database and are typically easier to get up and running. With workbench Domo doesn’t have direct access to your database but rather you have a local windows machine that will connect to your databases and then that wi does machine will send the data up to Domo giving only a single point for Domo to get data. As this adds an additional layer it can add extra administrative overhead. It depends on your needs which method you’d like to use.
Re: Cool blog post on DDX Bricks
Keen! Any indications on around when this would be available?
amehdad
Re: What's wrong with this case when statement / how do case when's operate on the back end?
The issue is because your function is only going to return the week number variable when work date equals today. You can do this much simpler by using this as your beast mode:
case when `Week Number` = WEEKOFYEAR(CURRENT_DATE()) then 'Current Week' else 'Not Current Week' end
You could also choose to use your workdate field instead of your weeknumber field by changing your beast mode to this:
case when WEEKOFYEAR(`WorkDate`) = WEEKOFYEAR(CURRENT_DATE()) then 'Current Week' else 'Not Current Week' end
You can use whichever is easier for you to read.
Re: Need help to connect a Microsoft SQL server to DOMO
Which connector are using in Domo? If you are using the Microsoft SQL Server Connector, you are going to want to look at this KB article and make sure you have all of the prerequisites addressed, particularly whitelisting IP addresses and ensuring your company's firewall has the appropriate ports open.
https://domohelp.domo.com/hc/en-us/articles/360043436173-Microsoft-SQL-Server-Connector