Best Of
Re: Moving Values One Row Down - Conversion Rates
@keeeirs10 Domo's MySQL is currently on version 5.6, which doesn't support lag. I would suggest using Magic ETL and using the rank & window tile and use the lag function in there. It will run very fast and is easy to put together. Here's the KB article on the rank & window tile if you haven't seen it.
https://domohelp.domo.com/hc/en-us/articles/360044876094-New-Magic-ETL-Tiles-Aggregate#3.
Re: Zoom Meetings Datasets - Meeting Subject
The connector does seem to be geared towards past meeting information. If you can find the right API call in Zoom's API documentation here: https://marketplace.zoom.us/docs/api-reference/zoom-api/
You could look at bringing it by building your own API connector, or try using the JSON No-Code Connector. You can also send the specific API to call to Domo Support and they will forward it to the connector team, who could look into adding it, but that may take some time.
Hope this helps.
Re: Colour Rules while comparing two columns.
Unfortunately, color rules require a fixed number and can't be based off of another value.
You could use a table card and then use HTML to color the text by creating a beast mode to look at another value, but it is certainly not the same visual as a line+bar chart.
Re: Unique ID within parameter
You could utilize the Lag function in the rank & window tile get the previous row's flag next to the current row's flag as another column. Then use the formula tile to overwrite the unique id if the previous and current flag are the same. Finally, you could use the rank & window again and use the row number function and partition on the account number field.
Hopefully I understood your request correctly and that this helps.
Re: Unique ID within parameter
@user027926 you can't use a lag function in a formula tile within Magic ETL. That is why I suggested doing a lag first with the rank & window tile to put the previous value next to your current value as a new column. Once you have the previous value in the same row as your current value, you could do the formula work that you want to do.
I'm not sure if it will help (and I tend to stay away from using them regularly) but you can do window functions at the card level. It is not enabled by default, so you need to as your CSM to "enable window functions in beast modes." You are wanting to do quite a few things, so I don't know that you can do it all at the card level, but thought I would mention it in case it is helpful to you.
Re: How to build card|total headcount based on the Hire date and termination date
Hi @Abhijith, for your first Q, as a start, this is an option to get total employees active:
COUNT(
CASE
WHEN status = 'A'
AND 'Hire Date' <= DATE_FORMAT(CURRENT_DATE(),'%d/%m/%Y')
AND 'Termination Date' IS NULL
THEN 'ID Number'
ELSE 0
END)
You could use 'COUNT(DISTINCT ... ' in the front instead.
To get the graph view by month, an option is to bring in another date field as a check of activeness (such as a 'login date' field or similar). This is where ETL comes in, a dataset that has a daily log of employees, that you can join by ID number.
amehdad
Re: Api fails for filters
Also how did you go with the 404 error? Did Support give reasons to why that was happening and how to resolve it?
amehdad
Re: Api fails for filters
You can have your Customer Success Rep help to accelerate the responses once you log the Support ticket.
amehdad
Re: Api fails for filters
Hi @sunny, have you shared the dashboard with the account that created the embed client authentication? The programmatic embed in your site would have an authenticating token attached to it, which is associated with a particular Domo account.
amehdad