ggenovese Coach

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.

If you don't need to loop through dynamic parameters then this should work, note that I have unchecked encoding on the values

I think what @ArborRose mentioned, and what I had missed, is that you're using the Dynamic URL option which adds the slash. Try using the Dynamic Parameter option instead.

Can you try making your parameter name "ApplyCreditDebit" and your value "True&$filter=FiscalMonth eq 12" and see if that works? Also, you may need to turn off encoded for your values. If you click the blue Encoding link and uncheck values that will prevent the connector from trying to encode your manual input

I realize you may only posting a subset of your data, but given what you've shared it seems as if you may want to union (in magic ETL it's called append) Table A and Table B. this would give you all the check in dates and property id's without duplicating bookings and capacity.

if you select the "Download from link to page" option, and then choose file type "Email Body as one row" it will create a column for the email subject line and a column for date/time received.

there is actually a TIME_TO_SEC() function that will convert to seconds, in order for it to be a decimal you have to determine if you want your value to be a fraction of a minute, an hour, or a day

If you use a Rank & Window tile in your ETL you can apply the DENSE RANK function to rank on MoveDate descending and partition by the Unit Id. This should give you a Rank of 1 for the most recent date and then you can add a filter to filter for Rank = 1

In that case you could use a Rank & Window tile in Magic ETL, using a Lag or Lead you can offset the prior month value onto the current months row so that you can calculate the variance

Trying to apply a number format in a beast mode can be limiting, especially if you want to comma separate the thousands. It might be beneficial to restructure your data in an ETL so that Revenue and Sales are in their own columns.

I prefer the way your data is currently structured, and I don't think it's necessary to pivot it in an ETL. The fastest way you can get a month over month variance, with your existing structure, would be to use a period over period card.

You might want to try selecting the "Offset by pages" option and then "No" in the pagination configuration, where it asks if the data contains the total number of pages, that has worked for me in the past. This works if you get a NULL response when you get to the last page, the connector will stop trying to keep fetching…

This is interesting, I did a test using the Domo Dimensions Calendar dataset using this variance beast mode: ( -- current value count(`d`) - -- previous value LAG( count(`d`)) over( Partition by `dayName` ORDER BY MONTH(`dt`)) ) / -- previous value LAG( count(`d`)) over( Partition by `dayName` ORDER BY MONTH(`dt`)) And I…

You could use an HTML table and then create a beast mode that pulls in an image of a checkmark CASE WHEN `myBool` then CONCAT('<div style="text-align:center"><img height="20px"…

Hi - your original beast mode was missing the second aggregation, you needed SUM(SUM(… CASE WHEN SUM(SUM(CASE WHEN `Ready Status` = 'No' AND `Previous Ready Status` = 'Yes' AND `Previous Ready Status` IS NOT NULL THEN 1 ELSE 0 END)) OVER (PARTITION BY `Case Number` ORDER BY `Case Number`) = 1 THEN '1 Time' WHEN…

Using the example data you provided I am getting a deduped SUM of 1,600 using the beast mode I provided earlier, if I add a total row it also evaluates to 1,600. Not sure why it isn't working for you. Going back to my earlier question, I'm curious what your DAX calculation would evaluate to if you were to add a Product D…

The DISTINCT expression in your DAX code is going to return a deduped list of qty values correct? Let's say for example, two items A & B both have a qty of 5, wouldn't the DAX code give you a total of 5 rather than 10? I don't know DAX so I want to make sure I'm interpreting that correctly.

Hi - when an item code is repeated, is the qty always the same corresponding value?