MichelleH Coach

Comments

  • This would be a great enhancement, especially since there is no notification when a report expires.
  • @LCash I second @GrantSmith's suggestion. I've run into a similar situation in some of my SQL dataflows where the result was rounding to the nearest integer because the numerator and/or denominator were integer datatypes. Forcing both to a decimal should do the trick.
  • @beatricetan21 The error is likely because the distinct count is inside of the second sum. Try removing one set of parenthesis: SUM(`Real Produksi TBS Tanaman Produktif (ton)`) / (SUM(`RKAP Luas TM (ha)`) / (COUNT(DISTINCT `Date`)))
  • @eriena You could create a beast mode so calculate the sum of pcs for each product to make sure that every product is visible in the table. For example you can create a Beast Mode called "Apple": sum(case when `Product` = 'apple' then `pcs` else 0 end) And this Beast Mode called "Grapes": sum(case when `Product` = 'grape'…
  • Hi @beatricetan21 are you able to run a preview of the dataflow? If you have any ETL tiles that aren't connected to an input/output or are unused?
  • The most recent Domo release added the ability to set a default landing page by user: https://domohelp.domo.com/hc/en-us/articles/4409575159191 However, it does not appear that this includes the ability to set the default by group.
  • Hi @user048760 , If the text you want to remove is always the "$" symbol then you could use a Replace Text tile in MagicETL to just remove that character, regardless of the length. Then you would need use an Alter Columns tile to change the datatype of your column from string to a decimal.
  • @DP_DynamicData I agree with @amehdad about the email option, this has also worked well for me. As another note on sub-dividing your dashboard, you are more likely to run into content being too tall if your "layouts" contain multiple cards that are vertically stacked. You can avoid the content too tall message by dragging…
  • @FME_Cavinder You could also create a table card that contains the Order #, Customer, and Order Date columns. Depending on your aesthetic preference, you could transpose the columns so that the header and text are aligned horizontally instead of vertically.
  • Depending on the purpose of your comparison, you may want to consider a Full Outer Join instead of a Left Join. That way you can check if records are missing from either dataset instead of just one.
  • @MosesWynn Are you checking for duplicates in any other other columns besides Case Number in your Remove Duplicates tile? It's possible that you could have multiple rows with the same Case Number if you are removing duplicates based on multiple columns.
  • @user007345 You will want to reformat your data so that each row represents a single product and month. Then when you upload the Excel file into Domo, you can create a line graph card with Month on the X axis, the value in the Y axis, and Product in the Series.
  • Agreed! Even with alerts it can be difficult to monitor for unexpected changes in how the data is processed, for example. Many times I find out about releases only after an end-user brings them to my attention, which is not ideal because it can lead to distrust of the product and impact adoption. Just knowing when releases…
  • This seems like a pretty significant business continuity issue. The only way around it I can think of would be to create a dummy Domo user dedicated to owning these dataset accounts, but that's not ideal if you have limited licenses.
  • @mhouston Correction... "Save As" is not within Analyzer, but can be found in the Sharing menu from the drill layer. My apologies.
  • @leeloo_dallas Can you show an example of what you want the output to look like?
  • For future users looking at this thread, you can save a drill layer as its own stand-alone card by clicking "Save As" when editing that layer in Analyzer. It will only save that individual layer, so any layers below that will still need to be manually recreated.
  • Hi @ramoshe I'm curious why you say it wasn't possible to create the mean in ETL. What have you tried and what was the result? Beast mode doesn't always like nested aggregate functions, so I think your best bet will be to fine tune that mean calculation in ETL.
  • This would be super helpful! When I've used waterfall charts for this type of analysis in the past, I've had to use Excel or a dataflow to structure the data the right way. It would be a huge time saver to be able to do this natively.
  • Yes! I would also love to have this ability in the Dataset table view. It would be super useful for filtering on an ad hoc basis, as opposed to pre-defined beast modes or segments.
  • @MarkSnodgrassAgreed! You can search for invalid calculations in Beast Mode Manager. Troubleshooting would be so much easier with similar functionality within Analyzer.
  • @DANIH If this is something you will use a lot you could also reach out to you Domo account team about implementing a fiscal calendar for your instance. As long as you can provide enough information for how your company's months are structured they can give you the option to use that calendar in your cards if you check the…
  • Hi @Liliana , Rather than trying to combine the date and time as text, I would suggest using this approach: Create a duplicate of the Time_Out column using a Combine Columns tile, using "None" as your character separating and selecting only Time_Out in the column list (Do not check the box to remove the columns being…
  • In your example, are you referring to the Salesforce credentials (i.e. "Accounts" in the Data Center) or the Domo credentials? Assuming you're referring to the Accounts it would be helpful to be able to change the owner of the Account (as opposed to sharing) and so they can enter their own credentials if need be. That way…
  • @mlevine_BRIT I agree with @tejusarora 's suggestion about the CVS option. Also, which type of card are you trying to send? I've found that you can see more columns when emailing a Mega Table (the "Table" in the Popular Charts section) as opposed to the HTML table.
  • I ran into a similar issue with two of my email datasets a couple weeks ago and submitted a support case for it. My IT department's best guess was that something was corrupted in the emails, since they were both based on automated emails from the same source system within a day of each other. I ultimately ended up closing…
  • Looking forward to learning how others use Domo and potentially sparking new ideas!
  • I recommend using the Domo Governance Datasets Connector to keep track of all your existing content. The "Datasets" report is especially helpful since you can more easily see names and descriptions of all the datasets in your instance. If you don't do so already, I encourage you to use a standard naming convention across…
  • +1 This would be incredibly helpful!
  • @Rob_E That was exactly it, thanks!