コメント
-
This isn't a solution for everyone, but you could screen-scrape the status page and extract based on incident. When the code sees the DIV containing incident details, have it send you an email. Takes about 60 lines of Python code. But you would have to have it running constantly.
-
You need to make sure the data partition is configured correctly. And make sure the partition key accurately segments your data without omitting relevant data. One of the things I watch closely in Domo ETL processing is duplicate records affecting joins. Number of rows can easily go whack. Normally expanding not loss. With…
-
Use lower to change all case to lower when comparing. CASE WHEN LOWER(Event_Label) LIKE '%thd%' THEN 'Y' ELSE 'N' END
-
Congratulations John Le!
-
@shreeyab - does the data look something like this…
-
I submitted a request for customizable padding when I first started using Domo. Why limit padding options for only embedded dashboards. All cards and dashboards should have options for padding, border thickness and color. These were among the first things available in html.
-
I haven't used pivot tables as source myself, so I can't answer that. But I don't think WorkBench wouldn't care as long as you can define the area of rows & columns. Example, I screenshot this image from an online pivot table example (below). If I set WorkBench to read the whole table I would expect it to fail. But you can…
-
I don't have the Location.ID or TransactionDateUTC in my data sample to play with. But they look to be further quantifying the condition. I can't test this, but what about something like this….
-
The error indicates that there's an issue with the way you're referencing positions in your Workbench job. Make sure your fields are in the correct order and that the data structures match. Such as date formats. Oh….also make sure you have your data laid out without merged rows. All rows should lay out with specific…
-
Sorry….should have explained my answer. When I review the way you have the data, you only want to count the repeat customer once per each customer that is repeating. We know they repeat when your cumulative sessions goes above 1. Thus we only check for 2 and count that. In my code, I am using SUM since my condition is…
-
As code block… SUM(CASE WHEN Cumulative Sessions = 2 THEN 1 END) OVER() / SUM(CASE WHEN Cumulative Sessions = 1 THEN 1 END) OVER()
-
I'm not sure how you are going to be to troubleshoot the download if you don't have access to the file. I use a regular SFTP program (such as WinSCP) to verify everything about files before trying to download or upload. Using provided settings, I can verify the file's existence before I try to connect. Make sure you have…
-
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.