Comments
-
Domo has their AI suite to utilize LLMs in a magic ETL.
-
you could create your own Date dimension dataset in an ETL and supply your own logic. Then you can ties that y to your datasets to get your custom calendar information
-
You can try and utilize a window function for your date instead of '04/08/2023': MAX(`OrderHeaderLocalDate`) OVER () - INTERVAL 1 YEAR This will look across your entire dataset and get the maximum date and return it for each row.
-
Here's a regex version: REGEXP_REPLACE(`field`, '^(.+)\/?', '$1/')
-
To Edit Domo (DDX) Bricks you need to have the edit cards grant. Participant users don't have this. If you want users to create or edit cards you'd need to potentially create a custom role that mirrors the participant user but also includes the grant to allow them to edit Domo Bricks.
-
When using date variables we have to define a specific value, it'd be great if it would allow the selection of today as a default as I'm typically wanting to use today's date with the variables. This would also allow me to not have to keep updating the default date as it gets farther away from the current date.
-
Domo has Writeback tiles you can use to write data from an ETL out to another location. Google Drive Writeback: Google Enterprise Drive Writeback: Google Sheets Writeback:
-
currently this isn’t an option but I’d recommend adding this to the idea exchange
-
@MichelleH - Have you tried turning it off and on again? 🤣
-
I'd recommend adding a new idea in the idea exchange to allow the NetSuite Analytics connector to use the new Connect Browser instead.
-
When doing Period over Period analysis I recommend restructuring your data to make visualizing your data easier. I've done a write up on this previously here:
-
Per Dates inserted into the table need to be formatted yyyy-MM-dd'T'HH:mm:ss.
-
I've found that refreshing the page typically will load the page's contents.
-
I'd recommend reaching out to Domo Support with a ticket as this appears to be an issue with the connector and they can get access to the code to help diagnose the issue better.
-
Have you attempted to do the average in a beast mode? SUM(`Work Hours`) / SUM(1)
-
I'd recommend logging a ticket with Domo Support to have them look into the connector as it sounds like a possible bug.
-
Have you tried something like: CASE WHEN (`Variable`-`Date Updated`) = MIN(CASE WHEN `Date Updated` <= `Variable` THEN `Variable`-`Date Updated` END) OVER (PARTITION BY `Opp Name`) THEN 'Closest' ELSE 'Exclude' END And filtering on the beast mode = Closest? Regarding your beast mode do you have any aggregation that's being…
-
Hi @MargieDomo - I'd recommend a beast mode like This will allow you to calculate time differences and format it
-
yes you can put the unmasked field in the tooltip on your card and then set the hover text to reference the tooltip field you used
-
Domo did announce at Domopalooza a new Beta for an ON clause in Magic ETL join tiles you might find helpful and valuable. You can read up on it here:
-
@ccccc4 It's having multiples of the same buckets because likely you're using another field in your sort or chart that doesn't appear in your FIXED function. Also you'll need to aggregate yout aggregate as @marcel_luthi points out. If you had some anonymized data for us to work with, that would be helpful.
-
Alternatively you can update your recursive dataflow so your input goes directly to your output, pull in ALL of your data in the input dataset, then change the version of the ETL back to the prior version with the recursion in place.
-
You're close, you'd need something like: `Pipeline Open` - LAG(`Pipeline Open`) OVER (ORDER BY `Snapshot YearWeek` DESC) LAG only takes 1 or 2 arguments, the field name and the number of rows back (optional - defaults to 1)
-
@NoahFinberg - Are you able to answer this?
-
Currently this isn't an option directly within Magic ETL but would be a much welcomed addition. I'd recommend adding an idea to the Idea Exchange for this. You could output your dataset before and after the pivot to new datasets and compare the difference in a more manual way.
-
The CLI is useful to do a lot of things in a scripted manner without having to have a lot of technical know how dealing directly with APIs. It can help automate a lot of processes as necessary as well. If you create a script with all of the commands you want it to run on individual lines and then pass that into the jar…
-
Add the beast mode to the filter section of your card and then filter for 'Yes'.
-
I'd agree with @brycec, the Domo connector isn't flattening your data so it's returning List as the value instead of breaking out each of the values within the list in the JSON. Use the JSON No Code connector to format the data as you need.
-
using a CONCAT will make you number a string and will cause it to lose any formatting. You can do this via a beast mode. I’ve done write ups in the past on this depending on the format Full number: Abbreviated version:
-
When I'm developing ETLs I like to be a teapot - Short and Stout. Short Reduce the dataset size to the smallest you need before doing any more processing. Have a filter tile be your first tile or use a Dataset View to pre-filter your dataset and then use that as your input (this will cause less data to be transferred to…