mhouston Contributor

@utkarsh when you say you are getting a cartesian join what does your output look like vs what are you expecting? based on what you've said, I'd expect your output has 1 row for every row in input 1. so if you have two rows for department A in input 1, and 1 row for department A in input 2, your output will have two rows…

@utkarsh what are you expecting your output to look like? Do you have multiple rows per department in input 2? are numerical column 1 and column 2 related in any way? I'm assuming you are doing input 1 left join input 2 on department - is that your setup?

@ddodd I would probably reach out to support. As a side note the excel plug-in is a different piece of functionality than the straight file upload in Domo, I'm not sure if the plug-in would impact this. I know when you use the API to upload data into Domo you lose that settings option, and I wonder if the same is true with…

@ddodd did you upload this using the file upload in domo? you should see settings as the fourth option (after Overview, Data, and Cards). if you used workbench, you will have to go into workbench to find the append option.

@Jack_Kaye it looks like you can get this from the Domo Governance connector in the Datasets History report. That has run time, as well as start and end time. You could filter on type to get just the workbench type datasets.

@LiliRestrepo adding the target="_blank" argument in the HTML code should do this for you. It would look like this: CONCAT('<div><a href="', 'https://yourinstance.domo.com/datasources/', `Dataset ID`, '/details/overview', '"', '"target="_blank">', `Name`, '</a></div>') ^^This is one I use in our instance to provide a…

@JunkDoom I have been told by our Domo account team that the dataset views do not count against your row limits on the warehouse. I would love to know if you get any other clarification from support.

@sarahi6 because you have start and end date in your group on columns, you are only finding the average time between purchases on the same start and end date. I am assuming you want to find the average time between purchase by customer, so you will want to just group on customer id (remove the start/end date columns).

@NathanDorsch you'll have to do it in the beast mode. @GrantSmith has a writeup on it here, and video link where he walked through it: https://dojo.domo.com/main/discussion/52677/domo-ideas-conference-beast-modes-number-formatting#latest

The SAVE in your screenshot is to save the dashboard. The DONE for a notebook card you will see if you are in the card details view and hit edit: With notebook cards, you can also click directly into them while viewing the dashboard (in a view mode, not in the editing mode) and click off and it should save. It sounds like…

@meekey the OVER clause tells you what to partition by - in your case I'd assume you'd want to do it on your asset and then order by date descending so you could find the last 3 sales for each asset. Something like: lag(sale_price OVER asset ORDER BY sale_date desc) I think you may have to reach out to your CSM to get the…

Can you screenshot where you are seeing "unable to load"? I am having trouble understanding where you are seeing an error if you are seeing everything as green and succesful.

@WorldWarHulk if you go into the history of your dataflow, you can click on the status button for more details:

@jkuleszynski this would be good to submit as an idea in the ideas exchange

@ozarkram you can do this using the instr() and left() functions. You use instr() to find the first space, and then use left to take everything to the left of that index. The formula looks like this: left(fieldname,INSTR(fieldname,' ')-1)

@Musetti I think this is currently in beta - they presented on the functionality at the user group community event. You can see the recording in this post: https://dojo.domo.com/main/discussion/55230/june-2022-user-group-recordings#latest

I think it's not working in your pivot table as laid out because you have the difference column underneath your larger categories of ACTUAL and BUDGET (so in the ACTUAL - difference, the only data the beast mode has is actuals). The way we've implemented this is using an HTML table and just creating a beast mode for…

I would do this in an ETL by filtering your dataset to this monday, and then using a second branch, filtering to last monday. Then you can right join last monday to this monday on date, po number, and schedule code. You can use a formula tile and set it to "new" when the left side po number is empty, and "old" when the…

@Raj did you look under tables in the chart type drop down?

@Banff_BIAnalyst you will probably need to put in a ticket with Domo Support. I had this same issue a while ago, and if I remember correctly, they had to modify something in the registry. They also told me that the workbench sync was not developed to work with synced OneDrive folders.

@ozarkram the easiest may be to do this in an ETL - you'll want to load the excel file into Domo (i.e. via the excel file upload) and then in ETL do an append between your excel dataset and your workbench dataset. If your excel file columns are already formatted the same as your workbench dataset, you could do this in a…

You can't combine two cards into one. If you have a revenue dataset and an expense dataset, you can append them and then you can build a card that has both revenue and expenses.

@ozarkram How is the rest of your card configured? Do you have any sorting applied? I've had this happen if I've created a beast mode like that but then sorted on the actual date field.

How large is your dataset? I believe this error is typically seen when your dataset is larger than the rendering limits on the card - all your data is there but your visual gets truncated. (see kb article for limits: https://domohelp.domo.com/hc/en-us/articles/360042924214-Card-Building-FAQs)

Domo has documentation on this : https://domohelp.domo.com/hc/en-us/sections/360007334233-Visualization-Cards You can also go thorugh the courses in Domo university: https://learndomo.domo.com/pages/13/learning-home

If it's a tabular report, you should be able to pull it through the salesforce connector. Otherwise you can use the connector to pull the data that powers your salesforce report and you can build/rebuild the logic in domo. https://domohelp.domo.com/hc/en-us/articles/360042927914-Salesforce-Connector

You can do this via a recursive data flow - your daily update would be a replace dataset and you'd have a second dataset that has your 8 days historic data. You can refer to the kb article for details on building it out:…

@ElliotGitter it looks like in your old way you weren't actually using the id in your ds_update function - reading your code it looks like testdata is a dataframe (ds_get returns a dataframe, not an id), and that's why you were getting an error.

@ElliotGitter where is your dataset coming from? Is it updating from somewhere else too? Once you've created the dataset using the API, you can always update it using the API (it's not like everytime you run your python script you have to create a new dataset to update). If you can create a new dataset using the API,…

Great! If you can mark the answer as accepted, it will help others in the community that have the same question.