GrantSmith Coach

You'll need to reach out to Domo Support to see if they can get you a more detailed answer as likely something is happening in the backend.

Because how Domo processes the data with the Pivot table you can't have your data elements display positive but your total negative and vice versa. I'd recommend logging an idea in the idea exchange to allow for this.

This is because Domo interprets all dates as UTC when they get imported. If your SQL server is configured for a timezone other than UTC you can use a date transform in your workbench job configuration to specify which timezone you're importing with.

Private Embed is built around the assumption that a users has a login and access to Domo and is built using a user model. A public embed is around an embed model where it counts the number of times the page is displayed and doesn't require a user to log in but will expose your dashboard to anyone who has access to the…

If you're on consumption it should be included. If not your domo administrator or customer success manager would be able to get the answer for you.

I'd recommend logging a support ticket for this issue.

Since your FY starts in February, you'll need to re-order your month numbers so that Feb = 1 and Jan = 12 (shifting the month numbers down by 1) CASE WHEN `Month Number` = 1 THEN 12 ELSE (`Month Number` - 1) END

You can try and use the FORMAT function to format your Date field to a string in the format you want: FORMAT(`date`, '%H.%s')

https://community-forums.domo.com/main/discussion/comment/100120#Comment_100120 You've got a COALESCE inside your COALESCE and you don't have your parenthesis properly terminated / closed. Try copying the forumla I posted directly above. My original formula had an issue. I've updated it.

You're subtracting a negative number so it ends up adding them together which is why you're getting 105 which is the span between your two numbers. It sounds like you want to take the difference of the budget and the absolute value of gross profit: SUM(COALESCE(`Budget GP`, 0)) - ABS(SUM(COALESCE(`Gross Profit`, 0))

COALESCE will work in either a Beast Mode or a formula tile or custom group by aggregation logic in Magic ETL.

@hollyrene1225 - I recommend restructuring your data so that you have multiple periods within the same dataset. I've done several writeups on this and it allows you to show multiple periods on the same graph. You can find more information on how to do this here:…

You can coalesce the values to default to 0 if they're null: SUM(COALESCE(`Budget GP`, 0)) - SUM(COALESCE(`Gross Profit`, 0)) Edit: updating the formula.

You can also use the Date Selector on the page as well to select a specific granularity on the graph. Alternatively if you want to allow the user to display the MoM, YoY and WoW on the same graph you'll have to restructure your data. I've done a write up on how to do this here:…

You can use the pfilters get parameter in the URL link. You can find more documentation on it here: https://developer.domo.com/portal/buk5zwk1pvjwh-url-parameters-in-embedded-content#pfilters 2. In your URL you can have it open in the same window with target="_self" <A…

Currently the maps don't support highlighting just the states with a border. You could attempt to create your own custom map with the states having the border applied already and then just display the chart. You can read up more on custom charts here: https://domo-support.domo.com/s/article/360042924454?language=en_US

You can use the group by tile to group based on the Position Owner and do a count. Then, do another group by tile to do it based on the candidate owner. Once you have those two, you can full outer join them together based on the Owner name. Finally you can fill the count field into a formula tile and to an IFNULL function…

A more straightforward method rather than multiple CASE WHEN statements is to use SPLIT_PART SPLIT_PART(`Fruit`, ',', 1) -- First in CSV SPLIT_PART(`Fruit`, ',', 2) -- Second in CSV SPLIT_PART(`Fruit`, ',', 3) -- Third in CSV

@Data_Devon It depends on your use case. Having your columns wide will allow you to consume fewer rows overall, potentially reducing your costs. On the other hand, Domo likes things as rows to deal with filtering. If you want to filter your records based on the City, then you'd need to pivot your locations stomore easily…

I'd recommend logging a ticket with Support to have them help diagnose your connector issue as they own that connector.

Have you tried redirecting the user to the same URL but utilizing an empty pfilter get parameter?

If it's not included in the standard connector you could try and leverage the JSON No Code OAuth connector to pull this information.

Have you inspected the network traffic to determine if you're getting an error with your JavaScript code used to save the records?

Sorry getting my languages mixed. You can use NOW() instead of TODAY()

You can use a beast mode calculate if it's a future date: CASE WHEN `StartDate` > TODAY() THEN 1 ELSE 0 END Then just filter for 0 in the beast mode.

In the buildForm function, you'd need to set the input box size conditionally based on the key field.

AppDB should update every 15 minutes. Do you have "syncEnabled" set to true in your manifest? For reference: https://developer.domo.com/portal/1l1fm2g0sfm69-app-db-api

Change Type of Values from Number to Text

You can use a window function to do a lag LAG(`Action Time`) OVER (PARTITION BY `Ticket Number` ORDER BY `Action Time`) This can also be calculated using a Rank and Window tile in a Magic ETL Then taking that you can calculate the time difference: SEC_TO_TIME(UNIX_TIMESTAMP(`Action Time`) - UNIX_TIMESTAMP(`Prior Action…

You can use a case statement to convert the 1 to 'Priority': CASE WHEN `field` = 1 THEN 'Priority' ELSE 'Non-Priority' END