Comments
-
Hi, I think there is no such function. This is a good subject to take to the iDEAS forum! Regards
-
I think the datacentre visibility is linked to the type of user: https://knowledge.domo.com/?cid=controlaccess As for PDP see please : http://knowledge.domo.com?cid=pdp Hope this helps
-
I think that is not possible to share a WebForm as Card. The only way i can see someone editing it is through the DataCenter. Maybe you can take into account using a googlesheet as a origin for a dataset, this way everyone with access to that sheet could edit it! There is a Native google sheet connector in DOMO. Some more…
-
You can edit the webform dataset whenever you want to.
-
Only the Webform datasets and the cards connected to it are afected by the changes. Hope this Helps.
-
Hi, From what i can tell there are no Cards with input capabilities in DOMO, the closest you can get from my point of view is WebForms. Some more information here : http://knowledge.domo.com?cid=updatingkpidata Hope this helps.
-
Hi, Either the Excel connector or Workbench are the way to go. Both allow to set the update frequecy. If your file is on premises, i would personally use the workbench tool. After the excel has been uploaded every card connected to the excel dataset or any dataset descending from that one will automatically update. Hope…
-
Hi, You will have to use a dataflow. You can use redshift dataflow to join the two tables, something like: Select Sales.* , Goals.MonthGoal, Goals.YearGoal From Sales Left Outer Join Goals ON Sales.salesperson= Goals.Salesperson AND DATEPART(y,Sales.Date) =Goals.Year AND DATEPART(mon, Sales.Date) = Goals.Month This will…
-
That is because you are just suming values from your invoices based on your card date filters. You have to take the beginig inventory into account or do a reverse calc from the end inventory if you have. I think this would be easier to do in a Dataflow. Hope this helps
-
Can you show me your BeastMode?
-
Hi How are you Filtering the data? Card Date Range? BeastMode?
-
Hi Where do you want to pull the data from?
-
Hi, Have you tried using DATEDIFF in a BeastMode : DATEDIFF (Completation_Date,Initiation_Date) This will give you the difference in days between the two dates, Hope this helps.
-
Hi, Something in the line of the folllowing Beastmode should help you (if i uderstand your question). SUM (CASE WHEN Quantity_Coming_In > 0 THEN Quantity_Coming_In WHEN Quantity_Coming_Out > 0 THEN Quantity_Coming_Out * -1 END) This could have to be adjusted to your data reality. Say somethinh if you need more help.…
-
Hi For the DOMO usage datases, I think you will have to reach out to support in order for them to create the "Domo Metrics datasets" in your instance. This was what i did some time ago. In those datasets there is one that can in some degree help you with your first question "Card Usage with Datasource and Owner…
-
Can you share some more details on how you are configuring it? And how your data is organized? Regards
-
Was not counting with dates in diferent years Try like this: (DATEDIFF(DATE('EndDate'),DATE('StartDate')) - ((WEEKOFYEAR('EndDate')-WEEKOFYEAR(StartDate))+((YEAR('EndDate')-YEAR('StartDate'))*52))*2 - (CASE WHEN DAYOFWEEK('StartDate') = 7 THEN 1 ELSE 0 END) - (CASE WHEN DAYOFWEEK('EndDate') = 1 THEN 1 ELSE 0 END)) It will…
-
Hi, The lack of sleep was getting to me last night (In my side of the planet). Here is a Simplified version of the beast mode : (DATEDIFF(DATE('End Date'),DATE('Start Date')) - ((WEEKOFYEAR('End Date')-WEEKOFYEAR('Start Date'))*2)- (CASE WHEN DAYOFWEEK('End Date') = 7 THEN 1 ELSE 0 END) - (CASE WHEN DAYOFWEEK('Start Date')…
-
From my point of view your average application is ok. What do you mean by "But it doesn't seem to be working as my # of days goes up instead of down“ Your lead time should be the number of business days since creation of order to invoice date, am I right?
-
I think that should have worked . Please verify the beast mode again : CASE WHEN YEARWEEK(`End Date`) = YEARWEEK(`Start Date`) THEN ((DATEDIFF(DATE(`End Date`),DATE(`Start Date`)) - (CASE WHEN DAYOFWEEK(`Start Date`) = 1 THEN 1 ELSE 0 END) - (CASE WHEN DAYOFWEEK(`End Date`) = 7 THEN 1 ELSE 0 END))) ELSE…
-
Are you applying the creation of the application date to the start date, and current date to end date ? I have this beast mode working on several scenarios...
-
Hi, I think that you are trying to accomplish an upsert. Update historical data with Delta data and add new rows if they exist, assuming that the historical table and delta table schemas are identical. This will give you a new output dataset containing the historical data upserted with the delta data. You cas use the…
-
Hi, Try this beastmode : CASE WHEN YEARWEEK(`EDate`) = YEARWEEK(`SDate`) THEN ((DATEDIFF(DATE(`EDate`),DATE(`SDate`)) - (CASE WHEN DAYOFWEEK(`SDate`) = 1 THEN 1 ELSE 0 END) - (CASE WHEN DAYOFWEEK(`EDate`) = 7 THEN 1 ELSE 0 END))) ELSE ((DATEDIFF(DATE(`EDate`),DATE(`SDate`)) - DAYOFWEEK(`EDate`)-(7-DAYOFWEEK(`SDate`)))*2) +…
-
Beware of using concat's in summary numbers if you want them later to be imported by Powerpoint Plugin. It doesn't import summary numbers originated in concats.
-
Hi. I don't know if window functions can be used in Magic ETL. And i can't see any way for a bestmode to get previous record values... But we never know!
-
Hi, I would make a transformation in a redshift dataflow in order to get the odometer value in the last reffil. Like this : Select *,NVL(LAG("odometer mileage") RESPECT NULLS OVER (PARTITION BY vehicle ORDER BY date),0) PreviousOdometer from tst_dojo_gas Then you can in a BeastMode get the Distance Traveled : `odometer…
-
Hi, Let me see if i can help, Where did you change the column Name? In workbench/Dataset Jobs/Dataset Schema\ Destination Column? What type of dataset is it?
-
Also there is a kind of a bug here, because even if domo takes the values in the first column into account while calculating the max and min values, it does not apply the interval color to the first column. You can verify this with a simple swap of the columns. Hope this helps!
-
I Think i know what is going on. Domo is using the year number to calculate the intervals of your heat map. One way to avoid this is no to allow Domo to do this by making impossible for Domo to convert the year to a number. You can achieve this by using the following beastmode instead of the year field: Concat(' ',`Year`)…