Comments
-
If you just remove the pipe symbols then you'd end up with a mix of "Company A", "CompanyA","Company B", "CompanyB" etc. so you'd need to replace pipe with a space. But if you replace the periods with a space then you'll have trailing whitespace. So I'd suggest you have two nested REPLACE() functions so that you can handle…
-
I don't think that it's possible, however a work-around might be to place your translated value column in the tool-tips so that when one hovers over the bar they can see the value in their home language.
-
If you make Following = 0 then you will get a running sum, it will sum all the preceding records in the partition and none of the following records. If what you were wanting was no frame at all, so the total for each partition placed on each row in the partition, then I find it's best to use a group by and join the sum…
-
Yes this is also really annoying for JSON connectors, so many options to reconfigure when all you should have to do is change an endpoint!
-
Hi @Arthi Annadi - You can view the impact of the policy, the knowledge base article I shared demonstrates that. Also, as an Admin, you can also view the impact of the policy by clicking the badge looking icon at the top of your dashboard and select the policy to preview. One note however, is that this functionality…
-
I reviewed the knowledgebase article and it looks as if you've set up everything correctly, have these datasets ran successfully since the update method was set to append? That's the only thing I can think of that might cause this. KB article I'm referring to:…
-
I feel that PDP is the best option given the requirements you listed
-
it looks like you're not using the replacement variable in your SQL statement it should look like this: SELECT id, name, source, dateAdded FROM tablename WHERE id > !{lastvalue:id}! ORDER BY id ASC and then make sure to seed your replacement variable with an id that you would like to start importing with, then once it runs…
-
Hi - Is sounds as if your data is not set up for this, I would recommend using Magic ETL. The steps would be: Add a Select Columns, choose your conforming dimensions and your Facebook specific columns rename Facebook Engagements as Engagements, rename Facebook Impressions as Impressions, etc. Add a Select Columns for…
-
I would suggest using PDP's to restrict what the users can see in the dataset https://domo-support.domo.com/s/article/360042934614?language=en_US
-
If Account Name is not common to both datasets that you appended together then that might explain why that's happening, because you'd have a row with the account name and then another row for the NULL account name. Or for that matter if the account names are even slightly different, extra spaces, or if one is upper case…
-
it's easy to miss! Hope that works for you!
-
Yes, in the config for the append tool you can choose the "Include All Columns" option
-
In Magic ETL you would append these two sources together into a combined output. The append tool will line up your columns by matching names so that you can then build a card off of the dataset that groups by Date, Member, Invoice and SUMs the Sales Amount and the Freight Amount.
-
Ah, thank you for that additional information. I mocked up a page and can confirm that I am seeing the same behavior. When the bar chart on the right has more than one week then I can click on the axis and filter the page to that week. However, when there is only one week showing then clicking on the axis no longer filters…
-
Hi - I shared a beast mode that you can use in a card, not an ETL
-
In your example, are the segments in your By Week card (Live, On Demand, etc) equivalent to the Business Group that's highlighted or the Pres_Name filter that's highlighted?
-
Having the date selector values available as system variables is exactly the kind of thing I was hoping for when I made this enhancement request, please vote for it if you're interested in seeing this functionality available.
-
The connector overview says "This connector is provided by Yext. Please direct all inquiries for support to Yext" Also, the Yext documentation for the Review Management API says "NOTE: Not all publishers' reviews will be included in the response. For more details, please contact your Account Manager." So you may have…
-
Without using the query option, I don't think so. However, you shouldn't have to load 3 years of data for every load. You can pull 3 years based on transaction date one, then set up a recursive etl, and then finally change your connector to incrementally pull in modified records with whatever window you feel is…
-
The link isn't working for me for some reason but I'd love to upvote it! Are ideas that are from 2017 no longer available to upvote on?
-
there's a FUZZY_PARSE_DATE() function in Magic ETL, I tested with the string '/3/31/24/' and it converted it to date without an error
-
If you haven't tried this already, the domo governance datasets would work in this situation. There is a Cards & Datasets report, it's pretty easy to build a card with links to the cards used by a particular dataset using the report. However, having the image of the card is really nice so making it a part of the UI would…
-
I think you have to do this in an ETL, because REGEXP_REPLACE() doesn't work for me inside of a card. LENGTH(REGEXP_REPLACE(`sample`,'[^A-Z]',''))
-
Can you post a sample of your data? It sounds as if you're keeping prior weeks sales data but not the prior weeks quota, is that an accurate assessment?
-
You're right, in hindsight it does seem redundant! I guess I was thinking by minimizing the rows by filtering would ensure that you'd get the correct results. However, now especially because you want to add YTD on the same card it seems like you can handle it all without any special filtering.
-
Variables are pretty awesome, especially for the sort of reporting you're doing where there are a fixed set of months that will never have to change and a limited number of years that need to be updated infrequently. Regarding your questions: You can update the years at any time What I sent earlier assumed a month number,…
-
There are a couple things going on 1. I'd recommend that Month and Year be variables, it sounds like they are filter cards built off the same dataset as your MTD/Last Year MTD card 2. Assuming that they are filter cards, then when you choose a Month and Year this filters your data to a single month and year which would…
-
I'd suggest adding an else so that you can determine whether the issue is that your WHEN isn't evaluating to true or whether the issue is with the replace
-
Also, another thing to consider is whether any downstream operations are being performed on the Amount Paid field. In other words, maybe the regex is working but there is another step in the workflow that is causing it to become a NULL value.