ArborRose Coach

If I understand your issue correctly, you want to make edits in a webform that is being replaced each morning. My method is to make a separate form and join it to the webform via ETL. My changes and fields are in the side form…joined to the main dataset. No matter how the main set changes, my values for Yes/No stay the…

You may also check to make sure the issue isn't with the cache or dataset access. If the user can't see the dataset, it may not let them see the card. For cache, go to the browser setting and clear cache to make sure that isn't an issue. Although I haven't had that issue recently, when I first used Domo it seemed my cache…

When you share a dashboard with users, all the cards on that dashboard inherit the sharing settings of the dashboard by default. So, if you shared the dashboard with a group of users, they should have access to view all the cards on that dashboard. However, when you add a new card to an already shared dashboard, it doesn't…

Thanks to Anna Yardley, I now know how to access the rich editor to paste code. Apologies.

@nickcorona - Did you do it as typed, or did you change the [] to back ticks? I typed brackets because I don't know how to make back ticks show up in these comments.

Sorry…I should have expanded on that. You say it gave a duplicate entry. When you give it an explicit list (stating each one) such as s.Name, s.Year…. and then you also include s.* you are repeating yourself. s.Name, s.Year are included in s.* and thus would repeat or duplicate. By explicitly specifying the columns you…

It might be having a problem with aliasing - using asterisk. Asterisk is a representation for all. SELECT s.Name AS State_Name, s.Year AS State_Year, s.Gender AS State_Gender, s.Id AS State_Id, n.Count AS National_Count FROM state_names s LEFT OUTER JOIN national_names n ON s.Name = n.Name AND s.Year = n.Year AND s.Gender…

Hmm. Okay, maybe we can simplify. SUM(CASE WHEN COUNT([PhoneNo]) > 1 THEN 1 ELSE 0 END) / COUNT(DISTINCT [PhoneNo]) * 100 We count the instances where a phone number appears more than once (indicating a repeat customer). We divide this count by the total count of distinct phone numbers (representing all customers).…

Unless it came out in a recent update, I don't think Domo has an option to disable the collapse functionality. But you could set to display all rows by default. That should prevent collapsing.

I don't recall seeing an option to force all entries to show. Then again, I don't normally see them hide. Can you reposition the legend to give more room to the legend?

How about this: SUM(CASE WHEN COUNT([PhoneNo]) OVER (PARTITION BY [Location.ID], [PhoneNo]) > 1 THEN 1 ELSE 0 END) / COUNT(DISTINCT [PhoneNo]) * 100

This might help. I did some testing a while back with pulling user info. I believe this is how I did it. The domo api can retrieve user information about the currently logged user.

Apologies for not following up. I got hit with Covid and I'm barely functioning. If you were able to get a preview, then your account should be working. I would look at how the paging is setup. You can try to debug using Postman, but I'm not familiar enough to help you. The browser also has a console which can be used to…

@marcel_luthi - I pondered that issue about a weekend action. In the data I'm working in today, it's not an issue and I can throw it out. But you could put some condition in your calculation. I haven't been able to look back on this formula as my day is getting crowded with other projects. But here's where I was last on my…

Oh..btw…I have gotten that error when my values were not wrong. Clicking the icon is like a refresh. Once or twice it was just a hiccup.

Assuming your account works….big assumption btw. You should see data selection. Enter your URL. There's an advanced link but it probably shows way over on the right. You can set parameters in advanced. Based on your comment, I am guessing the account part is okay. At that point you get to pagination, where the error is…

I use the Json No Code Connector all the time. What is the error you are getting? With the Json No Code Connector, you setup an account with access. Then configure with your URL, which should be the end point for the API call. Start with no parameters or something that limits your dataset length as a test. At that next…

Oh….I misread. Domo Dimensions Connector. I'm not familiar with it. I have some learning to do. Thanks.

Something like this maybe? CASE WHEN WEEKDAY(appointment_date) IN (2, 3, 4, 5, 6) AND CONCAT(MONTHNAME(appointment_date), ' ', DAYOFMONTH(appointment_date)) NOT IN ('January 1', 'July 4', 'December 25') THEN 'Working Day' ELSE 'Non-Working Day' END

If I comprehend the suggestion correctly - create a month of working days. Exclude holidays and weekends. So you have from 1 to however many useful days exist in a month. Use rank to number them. And chart those in comparison? So for this month, March 2024, we would have 21 working days. I'm not sure what the Domo…

@MichelleH - I'm not sure what you mean. Can you explain further or point me to some kind of example?

@marcel_luthi. Oh….what's your name preference?

Use a beast mode calculation that subtracts the amount desired. If you want to compare to previous 10 days, it would be DATE_ADD(CURRENT_DATE(),-10)). The number of days could be selected from a static filter.

If you use something like (SUM(units) OVER (PARTITION BY person) / total_units) * 100 It should keep the % constant regardless of filtering.

For filters, make sure all cards use the same dataset and have a common field. Example, if "Sales Rep" is your filter, make sure all cards have "Sales Rep" and that its the same data field in the set behind. It can also be part of a subset. In my case, I have a main set of transactions. If I join transactions with another…

I like the ability to delete a comment. But does it have to be so cryptic?

I agree. And something to do with indexing and prepping that data. I think many of us have this issue. We're used to environments like SQL where we can deal directly with the data. And in Domo, we find ways to bend it to our will. @Elibot - thanks for the info on the repair parameter.

I asked Domo advisers to workgroup with me to help me do what you suggest. After explaining what I wanted to do…I was told we couldn't. That's doesn't mean its not possible. It means between me and the other knuckleheads in the work session, we didn't know how. I really like what @Elibot is selling, but I'm not familiar…

I'm not sure about using a histogram. I'd use a bar chart. Note - my fake data does not exactly match yours. :) Creating SizeAsInteger with the formula : CAST(RIGHT(Size, 3) AS Integer) You can create bins (show above). Which seems customary for histograms and sizing.

It shouldn't have a problem with spaces if they are in the correct place. Beware of leading or trailing spaces. Many languages are picky about case sensitivity. Make sure you match the correct spelling and case. And check data types of your filters.