Best Of

Re: Starting a workflow from a Domo App

Ah ha! That was it. Changing the startName in the manifest did indeed fix the issue. Workflow started up correctly after changing it.

Thanks both of you for the help!

AJOslund

1

Re: Move multiple cards from 1 tab to another tab in the same App?

While you can't move tabs, you can use the multi select feature to move multiple cards at once from your page to another page. Use Command + Click on Mac or Windows + Click on Windows to select the cards and use the Add to option to add these cards to the app pages/dashboards of your choice at once.

khushboo_

2

Re: Arrangement in Bar Graph

You can use a beast mode to define a custom sort value to use in the sorting section of your chart

CASE WHEN `field` = 'Ro' THEN 1
WHEN `field` = 'Ac' THEN 2
WHEN `field` = 'Tr' THEN 3
END

GrantSmith

1

Re: Allow Brand Kit Font in App Studio

This feature is being requested by a strategic customer who is paying close attention to its branding guidelines and how they can be applied in Domo. If it’s just a quick feature switch type of situation, this would be a win for us.

dgriffiths

1

Re: Convert to timestamp

@vaco Timestamps and Dates columns in Magic ETL don't have a format. They will always be displayed in a way that is determined by the table or card you're looking at them in, along with your company settings like timezone and locale.

If you want to force a specific format everywhere, a string column is what you need.

As for the conversion failures, from your latest message it sounds like you have strings in this column that aren't Timestamps at all, like '—'. You'll either need to handle those strings specifically, like this:

case when process_timestamp in ('—', 'N/A', 'other value…') then null else cast(process_timestamp as timestamp) end

Or, if you can be confident that you'll never need to look at any value that isn't already a valid Timestamp in the column, you can simply use:

try_cast(process_timestamp as timestamp)

rco

1

Re: Percentage calculation using beastmode

@Jez Your beast mode should look like formula below.

SUM(IFNULL(`Reserve_Amt`,0)) / SUM(IFNULL(`Premium_Written`,0))

Instead of multiplying by 100 and adding the percent sign in the calculation, I recommend using the native Percentage formatting once the calculation is added to the card.

If this does not answer your question, then please provide a screenshot of your Beast Mode within Domo, as well as the error message.

MichelleH

1

Re: How do you change the field used for the date range on a card?

Some time has passed but Google suggested this to me, so dropping a comment for future web travelers who wrestle with a similar issue—grayed out date filter options.

My scenario was that one card (bar chart) displayed an x-axis with a calculated date, but the date filter had a different date column selected entirely. This was the desired outcome. A future built card using similar data would not replicate function because of the "default" behavior, as explained above in @mlb's note:

"As mentioned in the dojo article shared by you, I found out that, it is true. It is the functionality of Domo that, it uses the last date field added to your table card as the date range field but specially in table card. In case of bar chart, it always uses the date field which is in X-axis." and Domo claims it isn't a bug at all.

Well, that's sort of true.

For a bar chart, you can CAST the date field as a string with a DATE_FORMAT Beast Mode, and Domo charting then types and no longer overrides the date filter behavior. It's a situation where you have to unfortunately outsmart the tool, rather than the tool allowing the behavior and flexibility needed for design requirements.

What's even more confusing is the original card, the one I was trying to mirror, both the calculated date and the x-axis date were both typed correctly as dates, but this alleged default behavior was not applied. It's not clear if there's a secret handshake or order of actions to override the standard behavior, and it seems like a bug (even if we call it an 'escaped feature'). I'm not going to try to bark up that tree though — just cast display dates as strings and work from there.

Icing on the cake, Domo will (smartly!) pick up formatted date strings and allow date display strings under Properties to override, so you don't have to worry about y-m-d, m-d-y, d-m-y, etc. in pushing your string.

(Potential use case: Let's say you need to build a forecast each month that shows the next twelve months. You want to review last month's forecast versus this month's forecast using built-in date filtering, but all forecast dates are projected into the future. Domo, thinking its being helpful, blocks setting the date filter to 'Forecast Create Date' by defaulting to the displayed date of 'Forecasted Month'.)

Daniel_Rumschlag

2

Re: Programs Ending in the Next 60 Days

To get rid of dates that are older than today, you would want to modify this statement to look like this:



CASE WHEN DATEDIFF(MAX(Billing Month New),CURRENT_DATE()) >=0 
AND DATEDIFF(MAX(Billing Month New),CURRENT_DATE()) < 60 
THEN 'Program Ending' 
ELSE 'All good' 
END

MarkSnodgrass

1

Re: Need to get TOP 10 only

Sort on descending and then limit to 10 items:

ColemenWilson

1

Re: Tips for Setting up UKG Connector

If anyone is interested, we have developed a UKG Pro connector that automates pulling from the “Standard” UKG Pro APIs (found here: https://developer.ukg.com/hcm/reference/welcome-to-the-ukg-pro-api ). We can automate extracting Job History, Employment Details, Person details, Org Levels, Jobs, etc. It pairs well with the UKG Pro Reports as a Service Connector we developed that is also available to pull in data not available in the UKG Pro Standard APIs.

We are in various stages of development and service of connectors for UKG WFM, UKG Learning (Schoox), UKG Pro Recruiting, and UKG People Assist.

For further info: matt.hill@hcvue.com

matthill

1