GrantSmith Coach

I'm having similar issues as well. I'd recommend logging a ticket with Domo Support.

Because how Domo processes data (row-based) and your need to have custom date offsets you'd need to utilize an ETL to process your data. Instead of using the date from 1 year ago to join on you can use the event and the year (this year event) = last year (last years event). This would allow you to compare the custom date…

Group by your ID field, select the max customer ID value then join it back to your original dataset based on your 12 ID field. Then do a formula tile to choose either the Customer ID or the new Customer ID for your Customer ID field: COALESCE(`Customer ID`, `New Customer ID`)

I don’t think this it’s currently possible. I’d recommend logging an idea in the idea exchange

Multiply your value by -1 SUM (CASE WHEN DATE(`BatchTimestamp`) = DATE('2023-11-22') AND YEAR(`Month`)=2024 AND `FinancialCategoryName` LIKE '%CAPEX%' AND `Portfolio 2024_p`='Rejected' THEN (`PlannedCost`)*-1 ELSE 0 END)

FIXED functions only work in beast modes. You can utilize a RANK and WINDOW tile in Magic ETL to do windowing functions.

Here's an example where you can use the Calendar reference dataset from the Domo Dimensions connector: This example is getting 12 digits but you can change it to 8 if you want 8. After the join I feed it into a formula tile to calculate the rolling date: Date - Rolling 12 Months now has the date I'd use to visualize on the…

It looks like you're not passing in an Authorization Header. Here's some sample code I've used in the past which may be helpful: using System; using System.Net.Http; using System.Net.Http.Headers; using System.Text; using System.Threading.Tasks; class Program { private static readonly string ClientId = "YOUR_CLIENT_ID";…

Are your beast modes saved to the dataset?

Have you opened the variable in the beast mode editor window and then selected the "Add to Analyzer" checkbox in the lower right hand side and then saved it?

You'd need to either define all of the selectable weeks in a variable (which you must keep manually updated every week) or alternatively duplicate your data so that for every date you have that week and the past 8 weeks worth of data. This way when you filter on the selection date it'll show those prior weeks. You'd need…

I'd recommend logging a ticket with Domo Support for them to look into this.

With your post request, you need to also pass in the body, which would contain the user information you're attempting to add. {"displayName":"Users Name", "detail": {"email":"email@exmaple.com"}, "roleId":2}

I've typically utilized a VPN connection to have a secure layer to process data through on the Workbench server.

currently there isn’t. I’d recommend adding an idea to the idea exchange

COALESCE(`(A2) Posted Bill Rate`, `(A1) Original Bill Rate`) + COALESCE(`(B2) Posted Bill Adj`, `(B1) Original Bill Adj`) COALESCE takes the first non-null value in the parameters passed. So this is saying Use A2 Posted Bill Rate if it's not null, otherwise use (A1) Original Bill Rate. Add that to B2 otherwise add it to B1.

You might be able to utilize the Java CLI with the delete-rows command to delete specific upsert keys in your dataset. If you need to define an upsert key on your dataset you can use the define-upsert command. As a precaution, I'd recommend backing up your dataset and trying out on a copy first before modifying the…

There isn’t a straightforward way to trigger the workbench job outside of the server because it’s not known outside of the server. If you wanted to get super technical you may be able to configure that server to be exposed to the outside world and then potentially utilize a workflow and custom app to call out to that…

CASE WHEN `Lead Stage` IN ('Move In', 'Moved In', 'Deposit') THEN 1 WHEN `MOVE_IN_DATE` IS NOT NULL THEN 1 ELSE 0 END You can use IN to check for multiple values

Those are unique to each user in your instance. To create a client ID and secret you need to login to https://developer.domo.com/manage-clients and create an API Client (Client ID and Secret) As for the Embed ID, that will depened if you're embedding a dashboard or a card. You can select under the Share menu (box with…

Have you tried recreating a new connection to these files? Territoriale Reauthenticated the domo account used to connect to one drive? If you’re still having issues you may need to contact Domo support

if you're getting a bit all data is shown error is because Domo limits the number of rows a card would import unless you tell it to increase the rows. This is to keep the card loading quick and efficiently. You can increase the size but putting in a number larger than the default of 25000 or 50000 depending on the card in…

not all of your data is being pulled into the card due to the size of your dataset so it’s not finding your exact match. In analyzer under the filter section you can put in a number larger than 50000 to pull in all of your data. Alternatively if your ids are not unique you could aggregate your data in the card to get a…

currently this isn’t an option but you could either put this as an idea in the idea exchange or you could write your own custom app or Domo brick to do this interaction

You can use a beast mode to denote if the date is within the last 45 days and if so ignore it in the filter CASE WHEN `date` > CURDATE() - INTERVAL 45 DAY THEN 'EXCLUDE' ELSE 'INCLUDE' END then use that beast mode as a filler and only include the INCLUDE value

You can configure a MagicETL dataflow Output Dataset tile to use a Partition update method and specify the month field as your key. This will keep around any data that is no longer being pulled in from your source dataset. This is a beta feature so you may need to reach out to your account executive.

COUNT( CASE WHEN `Full-Time/Part-Time` = 'Full-Time' THEN 1 END) This case statement will return a value if your column is full time and then count that many values

if your data is exactly the same then you can swap it out but be mindful of any downstream triggers that may be reliant on your old data

you could also a summary number in your smart text to select the min and max date values Alternatively you can do this in a beast mode and add the beast mode as smart text

Have you attempted updating the dataset previously and it failed? It may be stuck in an updating state. You may need to reach out to Domo support to have them fix it in the backend