Best Of

If this is outdated, I would send an e-mail to support@domo.com and let them know what the current API call should be. It may take some time for the connector team to update the API calls, though.

You may want to look into the JSON no code connector and see if you can make that work for you. It is a nice universal connector to use.

MarkSnodgrass

1

Re: I need a beast mode that provides 2025 Sales % VS 2025 targets

@CK_16 The error can be resolved by rearranging the calculation so that the numerator and denominator of your beast mode each contain a single case statement within a sum like below.

sum(case when year(`trx_date`) = 2025 then `extended_amount` else 0 end)
/ 
sum(
  case 
    when `Product Category` like 'Product 1%' 
       and year(`trx_date`) = year(current_date()) - 1 
       and dayofyear(`trx_date`) ⇐ dayofyear(current_date())
      then `extended_amount`*1.055
    when year(`trx_date`) = year(current_date()) - 1 
       and dayofyear(`trx_date`) ⇐ dayofyear(current_date())
      then `extended_amount`*1.145
    else 0 
  end)

MichelleH

1

Re: How can we get the current date/time to be used within a Workflow?

That's a great way to handle it. You can also find a function in the Workflow Executions package that will give you metadata about the workflow.

I know the team has "system variables" on the roadmap, where some of these things will just be automatically there as variables that can be used…stuff like who started it, when, etc… There's also plans to expose syntax for things like current date right in string builder.

DanHendriksen

1

Re: Scheduled Report - Excel Attachement

@Jones01 That is correct. I am able to receive card-based scheduled reports as an .XLSX file, keeping all of the UTF-8 characters. I don't have an option to choose XLSX or CSV. It sends an XLSX file for all card-based scheduled reports.

mberkeley

1

Re: auto subscribe to an alert

Michelle's suggestion is a good one. You could do this with a workflow, but it would be a custom function to do the alert sharing bit. You'd also need to sort out the logic and determining how an alert (they can exist on datasets as well as cards) is related to a dashboard, which alerts should be shared and which shouldn't, etc…

DanHendriksen

1

Re: auto subscribe to an alert

@James_Lord I'd suggest sharing the alert with the same groups used to grant access to the relevant dashboards. You should be able to accomplish this without a workflow, and hopefully saving you some credits.

MichelleH

1

Re: Write back Task

I don't have the available time to work through an example. This is just how I would approach the problem. I would try setting up the webform and set permissions where owner is the logged-in user. Make sure it filters PDP to that specific person only. So feedback editing is allowed only for them.

If Domo won't allow it to be editable inline on App Studio, I'd attempt a custom brick. This isn't something for beginners, it will require code or some AI assistance to write. Either find a prebuilt form brick or create something custom using blank brick from AppStore. This will use JavaScript and html. Fetch tasks where owner is the current user. I tested the following in a brick and it can identify me as the user or give my id. JavaScript is case sensitive btw.

console.log(domo.env.userName);
console.log(domo.env.userId);

If you know the user logged in, you can filter a form to them. Retrieve table information from a dataset and render an input field for feedback on each row. On click, save the feedback back to a dataset (write-back).

const currentUser = domo.env.userName;


const userTasks = allData.filter(task => task.Owner === currentUser);

ArborRose

1