GrantSmith Coach

@Godiepi - It appears they don't have a closed at field as part of their API documention. The closest you can likely get is to check the updated_at field when a ticket has a status value of 4 or 5. This will cause the ticket to lose the resolved time if it ever becomes closed. You'll likely need to talk with Freshdesk to…

Hi @adithya You can refer to their API documentation: https://developers.freshdesk.com/api/#list_all_tickets (Search for 'Ticket Properties') Open: 2 Pending: 3 Resolved: 4 Closed: 5

You could leverage a scripting language and the web.exe executable to run the jobs and then determine if it succeeded or failed. To do that you’d likely need to read the JSON export (can do the export with the web.exe executable). Essentially you’d be writing another program to monitor workbench and have workbench kick off…

Just to reiterate I don’t recommend that method of permissions. PDP is the way to go when you need to filter data for specific users. Do PDP based on a specific group or groups and then add specific users to that group (or dynamically) Filtering and then sharing the dataset opens the possibility it could accidentally be…

They're just like any other dataset. PDP is the preferred method for restricting access but in theory you could filter the view and then only share it with that user.

Hi @technollygy the Magic ETL 2.0 Beta has a formula tile where you can just do a simple COALESCE function to default the values. The way you have it is the only real way to do it in Magic ETL 1.0. It's been in beta for a while. Talk with your CSM to see if you can be apart of the beta or you can wait until it's in GA.

You can use a beast mode to calculate the times and filter on results which return values within that result: CASE WHEN `Timestamp` BETWEEN CURDATE() - INTERVAL (24 - 7) HOUR AND CURDATE() + INTERVAL 7 HOUR THEN 'Include' ELSE 'Exclude' END CURDATE defaults to midnight that day so we're just subtracting a certain number of…

@AnwarBham Have you tried using the Domo Governance dataset for Datasets to do filtering? You can do beast modes / calculated fields on that dataset to do combo filters like you're asking about.

Hi @bdx You can do it with a beast mode which will be responsive to any filtering you apply to your card (the percentiles will be recalculated with respect to your filters) CASE WHEN SUM(SUM(1)) OVER (ORDER BY `Score`) / SUM(SUM(1)) OVER () > .2 THEN ‘Other’ ELSE `Name` END

Hi @Bianca_M There is an option to fill missing dates on the bar chart however it only fills dates between your first and last date. As such it won't exactly help in your case. You'll need to make sure the July date is included in your dataset. You can utilize the Date dimension data set from the Domo Dimensions connector…

Essentially yes. Domo does supply a Dates dataset in the Domo Dimensions connector which gives you a list of dates as a starting point you can modify with a view or ETL to do additional processing / adding of columns to.

Your best bet is to talk with your CSM to see if they can get an idea if this is on their roadmap or where it might fall since you’re looking for a product update from Domo.

Depending on when your quarters start you might want to think about using a date dimension table which has your quarters defined if it doesn’t start on Q1=Jan-Mar. You can use a view to join this date dimension table to your dataset and then pull in the quarter from your date dimension table.

Hi @bdx You'll want to try and import your data in batches if possible.

Hi @guilhermekido What does Teams expect the payload to look like? The webhook for alerts delivers messages in a specific payload format which isn't compatible with several applications (Slack in my instance). I ended up having to write a middle layer application which essentially took a JSON request and reformatted it,…

@user000253 Similar to your existing beast mode: CASE WHEN CEILING(`Process Temperature (DegC)`)<= 0 THEN 1 WHEN CEILING(`Process Temperature (DegC)`)<= 20 THEN 2 WHEN CEILING(`Process Temperature (DegC)`)<= 40 THEN 3 WHEN CEILING(`Process Temperature (DegC)`)<= 60 THEN 4 WHEN CEILING(`Process Temperature (DegC)`)<= 80…

Hi @user000253 This is because your bins are being sorted based on alphabetical sorting instead of numerical sorting (It's comparing each number one at a time in your value instead of the entire number). When I have bins like this I'll utilize a new beast mode which is similar to the original beast mode I used to create…

Hi @Joe_M I'm a big fan of DataSet Views. They allow for simple ETL operations (aggregation, filtering, joining - even calculated fields) and load in real time as they don't have to send the data off to be processed so they're typically much quicker. Another nice feature is that you can use them in ETL 2.0 dataflows so if…

Alternatively you can utilize an ETL to do the pivot for you as well. Assuming your data is in the format of: Date | Item Status | Count Field you can utilize a group by field and group by Date and Item Status taking the SUM of the count field (or alternatively if you have the raw data do a Count of that field). then toss…

Hi @enricopirazzini It doesn't appear there's a way to pull the audience network information with the currently available connectors. You might want to reach out to your CSM to discuss if they can enable the Facebook Audience Network Connector for you or if it's actually available.

The ETL would be more accurate and flexible in terms of how far back your last value occurred whereas the beast mode would only go back as far as you have defined.

The code above is for a beast mode. If you want to do it in an ETL, you'd need to use two separate tiles to add a constant called join column, set them to 1. Add a filter to one of those Add Constant tiles to filter out any records with a 0 value, then LEFT join those two together with a join tile (your main dataset on the…

Hi @rachelchorlton There's not a simple way to do this with a beast mode. You'd need to do this within your ETL to get the most recent non-0 number in your dataset. You could sort of hack a solution together using case statements and the LAG window function however you'd be restricted to the number of rows back you'd be…

One thing to note, window functions aren't available out of the box, you need to talk with your CSM to get them enabled in your instance.

Hi @Sam1 Sounds like you want an average across the entire dataset to compare against. You can utilize a window function to get this and then compare your average to to it. Overall percentage: SUM(SUM(`UniqueOpens`)) OVER () / SUM(SUM(`NumberDelivered`)) OVER () Putting it all together: CASE WHEN…

@trangnguyen You can utilize the Domo Governance Datasets (specifically Cards) and build a filter card based on the card names where you can serach based on test in the names of those cards.

Hi @Nick_Bertz Currently this isn’t possible to have a default radio button selected and filter the entire page. I think it is something that's on the roadmap to get implemented but who knows when that will be. I'd recommend adding it as an idea to the Idea Exchange. There was one submitted earlier to the Idea Exchange but…

It's how sorting works. The way to get around it is to make sure you have a record for every date and text combination in your dataset.

Hi @user12621 I believe what's going on is because you're missing data within some of your pivot table those values aren't included in the initial sort based on the date. For example: 1/1 A 50 1/2 A 100 1/2 Z 25 You're sorting on the date first so you'd have 1/1 come before 1/2. Since Z doesn't exist for 1/2 it pulls A…

@MarkSnodgrass, Federated datasets can't be utilized in an ETL. https://domohelp.domo.com/hc/en-us/articles/360042932974-Using-the-Federated-Data-Solution#1.2. @user095459 There shouldn't be much of a performance hit from a Domo standpoint. Do you have access to your database logs to see if your server is able to handle…