GrantSmith Coach

You can utilize the Java CLI and the backup-card command to export the definition of a card to a JSON then modify the JSON definition to include your color rules to include values which don't currently exist in your dataset. Then utilize the restore-card command to upload those changes to your instance. Make a copy of the…

The code is appending each record to the end. If you want to change it to add them to the beginning you need to use prepend: $table.find('tbody').append($row); Becomes $table.find('tbody').prepend($row); in the addRow function (originally around line 198)

Here you go: https://community-forums.domo.com/main/categories/ideas it’s another section on these forums.

You could possibly use a FIXED function and the FILTER ALLOW clause to only allow filtering on a specific date field when calculating your totals. Here's a link to documentation on FIXED function:

Currently this isn't possible with the default scatter plot. You can add this recommendation to the idea exchange to possibly add this to Domo's roadmap. Alternatively you could look into utilizing a Domo Brick to write your own scatter plot and allow for this type of line but that's a much more technical and involved…

To expand on @MarkSnodgrass 's answer you'll need to use the FILTER DENY or FILTER NONE clauses in a fixed function to prevent filtering from happening on the value. SUM(`Value`) / SUM(SUM(`Value`) FIXED (FILTER NONE))

Domo would suggest the Data Science package to allow for R or Python tiles to do the NLP processing in a magic ETL dataflow but it's an extra cost. You can utilize rdomo to extract data from Domo and process it and re-upload it (or pydomo if you're a Python fan). There's nothing currently out of the box to do NLP.

Currently the data table will only display the data that's displayed on the graph. There isn't a way to have it included in the included table without displaying it on the graph. You could have a separate chart for just the graph and include the data you wish there on the page. Alternatively you can suggest this through…

You can use a formula tile to populate a new user id column in your old dataset by just appending the @email.com with a CONCAT formula: CONCAT(`Old User Name`, '@email.com') Then you can use that new field to join to your new dataset and get similar records.

Good clarification @MichelleH @jtrollinger it should end up with something like this CASE WHEN `HdrParentItemCode` IN ('ZROUGHIN', 'ZWATER', 'ZSEWER', 'ZROCK', 'ZVANGUARD') THEN 'Rough-IN' WHEN `HdrParentItemCode` IN ('ZTOPOUT', 'ZGAS') THEN 'Topout' WHEN `HdrParentItemCode` IN ('ZTRIM','ZDROPIN') THEN 'Trim'…

Alternatively you could filter the rows for non null values, feed that into a remove duplicates based on your two ids and the use a join tile to join them back together based on the id fields and then rename the new category

If the category is the same across for each store and ticket I’d you can use a rank and window tile to get the max value of the category for a new column and then use an alter column tile to drop the old category field and rename your new category field

@Aag2023 there aren’t individual edit permissions currently within Domo for dataflows. Permissions are based on the input datasets. I’d recommend adding an idea to the idea exchange for added dataflow security

Only the first CASE keyword is needed you can remove the others but leave them when and clauses

You'll want to both kill the Workbench process and restart the Workbench service in services to make sure it's no longer running and attempting to process your data. If that won't work then there's always the Windows solution - reboot the server.

Or even simpler you could try and check the General > Reverse Color Direction option in the settings.

Try using a beast mode to multiply your value by -1 to flip the ordering and thus the color scheme. You can then also use the tooltip 1 for the actual value and display that in the tool tip / data value properties.

Can you post a screenshot of your code and the error your getting?

Hi @your_super_shawn , I'd recommend reaching out to the App Support team at domoappsupport@domo.com. They will be able to help resolve your issue. You can follow under How to Submit a Bug to help get an answer faster.

CASE WHEN COUNT(CASE WHEN `Event Type` IN ('Hearing', 'Vision', 'ASQ3') THEN `ChildPlusID` END) = COUNT( CASE WHEN `Event Type` IN ('Hearing', 'Vision', 'ASQ3') AND `Event Status Code` = 'Completed' AND DATEDIFF(`Event Date`, `OriginalEnrollmentDate`) <= 45 THEN `ChildPlusID` END) THEN 'Completed' END This is assuming…

Start with a day and see if that's returning all of your data.

Hi @shrikantdeshmane Is it a matter that it's throwing an error message or it's saying it succeeds but just doesn't update any records? What was the code you used to create the table xxtm_demand?

@gbrown Glad to hear it! If you could accept any answers that helped solved your problem so others can easily find the answers I'd appreciate it!

You can use a Rank & Window tile with a MAX aggregation to get the most recent date. You can partition by the project_number to get the latest date for each project.

You can replace the FLOOR(SUM(`random_number`)) on line 11 in the example with the beast mode that will format the value with commas. You can refer to the Number Formatting link I sent earlier.

@tlammie1806 Google restricts the amount of data it will pull in the APIs due to performance reasons. If you limit your request to a small enough dataset it will return everything, otherwise GA will return a sample of your data. You may need to pull data for a specific day to reduce the size and have GA return the entirety…

It's not possible to include an average when using a category series. You could create a separate graph to display the overall average next to your original graph.

Are you grouping by anything? Have you selected to graph by day or month in your date selector (upper right of the graph)? What type of graph are you using?

Here are a few posts on beast modes that may help you:

Agree with @MarkSnodgrass. To clarify you'd need to do this within a Magic ETL dataflow as a beast mode on a card won't support the multiple aggregations that would be needed.