ColemenWilson Coach

You could use the Domostats datset "DataSets History". It has a field called 'Bytes Inserted'.

You could try this:

This is not currently possible. You could submit this as an idea in the

That likely has to do with the page filtering - I see a filter icon in the first image (bottom right).

PDP is applied to drill down. If you are seeing data you shouldn't on drill down you will need to modify your PDP policy. If you can't figure it out and keep having issues please let me know and I'd be happy to jump on a call with you to troubleshoot.

You wont use the Cards Pages dataset. You'll use the Domo Goverance report titled: Cards. You will also use the Domostats report called App Studio App Pages I do know there is an effort to ensure all Domostats reports have the same data as Domo Governance reports so there is parity between the two. @DanBrinton Until then,…

Setting up the PDP right on the dataset will have no credit implications. PDP using the toolkit will as it requires a configuration dataset which will cost a credit every time it runs. The toolkit is great if you have many datasets with many policies. Directly in the dataset is great if you only have a few datasets that…

UPDATE: Found a way with the help of our Domo Admin. You can join two Domostats: Cards, and App Studio App Pages. Page ID is in both datasets.

@DanBrinton @Tasleema I think this may be a Domostats gap. I can't find a way to link this data in any way.

@ggenovese never heard of FUZZY_PARSE_DATE(), super helpful function!!!

Can you run a preview in your ETL and show the error you get there?

Gotcha! With a card embed it is not possible to remove the "Powered by Domo" but you could make a single card dashboard and embed that and that would remove the "Powered by Domo".

As shown in the error, there is a value '/3/31/24/' that is not in a date format or one that can be converted to a date. Either fix the value in the source data, or use a formula tile in Magic ETL to convert that value to '03/31/24' then use the alter columns tile to convert the string column to date.

It doesn't look like this is currently possible. I would suggest making this request in the

Hmm I am not seeing that for public embeds of App Studios Apps or Dashboards. Is this the type of embed you are doing:

Hmm I don't see that when I embed dashboards. Example: Can you share a screenshot of what you're seeing? Also how are you embedding and where?

So stoked to see the status change on this Idea!!!

In an ETL, isolate your quota data and filter so you only have 1 row per rep, per quota. Then join that back to all data on Rep = Rep. If you provide sample data with Rep, Quota, and sales amount fields I can build it in an ETL and show you.

So you want to compare the current quota, to historic sales data? If that is the case you can just join your quota by rep and then for every row of sales data the quota will join to it. You'd have something like this: Date Rep Sales Quota 1/1/2024 John 20 30 1/2/2024 John 25 30 1/3/2024 John 20 30 1/4/2024 John 23 30…

The quota field would remain, but previous quota values would be filtered out and you'd be left with the most recent quota amount.

LENGTH(Uppercase) - LENGTH(REGEXP_REPLACE(Uppercase, '[A-Z]', ''))

You can use 2 beastmodes: 1. This one will filter out anything that isn't Access Carrier. CASE WHEN `field` LIKE 'Access Carrier -%' THEN 'In' ELSE 'Out' END 2. This one will remove the text from the strings: REPLACE(`field`,'Access Carrier - ','')

Yes. In your ETL you can use a rank and window tile to assign a rank to the most current quota for each employee by date. It would look something like this: 1. 2. 3. Then in your card add a filter for the Rank Value field and set it to Rank Value = 1. This will keep the row of data with the most recent update date. Let me…

Yes. Would you mind sharing how your data is formatted? If you provide some sample data I can build the beastmode for you!

Huh. So as the input it is a date, but when using it in the ETL it is converting it to a text and not allowing you to convert it back to date? Seems like you have identified which date field is causing the issue, did you find the value '0/00/2024' in that column?

If you can change the type, the 2012-03-14 format is preferred. In Domo, navigate to the dataset and then inspect the schema. You'll be able to see the data type for each field. If you see a field that should be a date, but shows 'abc Text' Then that is likely where your issue is.

Where is your data coming from? If you can edit the value in the source system directly, you could change it from '0/00/2024' to a proper date. If that isn't an option, you could fix the data using a formula tile: CASE WHEN `DateField` = '0/00/2024' THEN '12/31/2024' ELSE `DateField` END

Are there other filters impacting the card? Could you share more to help troubleshoot?

Yes. You can do this using Color Rules:

Okay, were you able to get the count of candidates or do you need help with that as well?