MichelleH Coach

@javiermolina What logic do you need it to follow? If you change the Scale Market value types from "Manual", there are several options that would change based off your data, which would update as you filter the card. I would also remove the Min and Max values on the Value Scale so that the visible range will resize based…

@Kunal Do you have any aggregation on your Y-Axis field?

@Kunal You can still have the rank and window in your ETL. I'm referring to the sort fields that are applied to the card in Analyzer.

@Kunal You should not need to sort by your date field since Domo will automatically sort by whatever date is in the X-Axis. If you manually add a sort date without aggregation, you could see duplicate dates since it will try to sort by every unique date

@Jones01 Selecting two columns of the same name is bound to cause issues since SQL operates based off of the field names. In these situations, I would recommend specifying which columns you need from the right table like this: select A.*, B.`Column 1`, B.`Column 2` from `Table A` as A left join `Table B` as B on A.`id` =…

@NateBI I'm glad you got it working!

@NateBI You can still have created date in the card, but you will need to add 'batch date' first. Also, you may need to have the 'batch date' column further to the left than 'create date'

@NateBI This is usually because the "created date" field is being used in your card. Try removing it and adding the date field you want.

@Jones01 112k rows should not be enough to cause performance issues on the dashboard. More likely it would be caused by the number of cards, the granularity of the cards, and the internet connection/memory capabilities of your individual computer.

@Jones01 If you're unable to replicate it then it's possible it was just a temporary issue with the data preview.

@Jones01 Have you made any changes to your query recently? Or is there a UNION in your query?

@Jones01 Is your dataset set to Append? I've encountered this in the past when adding or subtracting columns and Domo adds data in the same column position, rather than by column name.

@Stuck I agree that this could be a useful feature. I suggest checking whether anyone has already posted this to the Dojo Ideas Exchange and upvoting it so that Domo's product team sees it. If it hasn't been suggested already, then you can create a separate post for others to upvote.

@crico Have you considered saving the quarter ranges as individual Filter Views?

@sarahi6 That would make sense that the "Avg Time Between Purchase" is the same, since the "First Purchase Date" and "Last Purchase Date" would be the same across all rows of the same Customer ID. If a customer has purchases on January 1, May 1, and August 1, then you would be comparing the difference between January 1 and…

Hi @sarahi6 can you please share a screenshot of your group by function?

@crico Since you are using multiple datasets, I recommend using dynamic date range filters and Filter Views. The global date filter is not tied to a specific date field, but instead uses whatever field is used in the Date Range settings of each card.…

Hi @NathanDorsch try removing the last "end" and see if that resolves the error.

Hi @aconway can you please give some more details about what you mean by timeframe? Do you mean you want to filter to rows where the date you specify is between the values in the Date A and Date B fields?

Hi @Sudershan which Jira connector are you using? Do the fields you need exist in other reports?

@jmmc I agree that ETL v2 is probably your best bet. Joins are generally very processing-intensive, so it's not surprising that a dataflow that joins 17 datasets would take a while to run. I'm not sure if this applies to your situation, but you could also see if there are ways to filter the datasets as much as possible…

Hi @jmmc how many datasets are you using in your ETLs and how much data do they contain? I recommend starting with this best practices article on the Knowledge Base: https://domohelp.domo.com/hc/en-us/articles/360042935434-Data-Processing-and-Tools-Best-Practices

@robdmitchell According to this KB article, the connector enforces UTF-8 encoding by default but it can be changed under the Advanced Options. https://domohelp.domo.com/hc/en-us/articles/360042931954-DataSet-via-Email-Connector

Hi @robdmitchell did you specify CSV as the file type in your Domo Connector?

Hi @Siddhesh_Bandekar you could try a beast mode like this, assuming the first 3 quarters have 13 weeks and Q4 takes the overflow: CASE when WEEK(`Date`) >= 39 then WEEK(`Date`) - 38 else MOD(WEEK(`Date`),13) + 1 END

Hi @nica_tc you would not be able to use the card itself as a dataset input. You should be able to use the dataset powering the card as an input to another dataflow.

Hi @dacorson I don't know of a specific limit on rank and window tiles. Could you please share a screenshot of the error you are seeing?

Hi @Jones01 you can do both using an add-on called the Domo Campaigns App: https://domohelp.domo.com/hc/en-us/articles/360042933494-Domo-Campaigns-App

@RajNadar What kind of comparison are you looking? Could you please provide a more detailed example of what you want to do?

Hi @nica_tc I don't believe there is a way to dynamically name columns in ETL, and having that many columns would likely be messy to manage anyway (one month's worth of data would result in 30 individual columns and you'd have to manually edit cards every time you want to add a day). I recommend keeping a separate date…