ColemenWilson Coach

Hi Jez, could you share a bit more information? Who will be the audience for this report? What metric are you wanting to show? Salary by employee? Salary by position? Salary by age? Or something else?

Gotcha, then multiple policies would be the way to go.

You can add multiple criteria by clicking ADD DATA next to the first criteria added. You can also add multiple policies for the same user/user group. I would also recommend contacting your CSM about Governance Toolkit. There is a tool there called PDP Automation that makes complicated PDP policies a lot easier to manage.

Hmm without logging in and troubleshooting I don't think I can help much more. I would recommend submitting a support case to Domo.

So you aren't seeing the PDP icon appear in the bottom right of those cards? And you've verified that the dataset powering that card does indeed have a PDP policy?

Are you seeing data you shouldn't? Or are you saying that the data is just wrong? I am guessing a filter is wrong and causing the issue not PDP. That would explain why the issue is on the dashboard level but not card level.

PDP is applied to a dataset and impacts cards built using that dataset, so it isn't a dashboard issue, but likely a dataset/card issue. Have you checked each card to ensure it is built using the PDP applied datasets?

BETWEEN is not supported in beastmodes only in Magic ETL formula tiles. You will need to rewrite the beastmode to be: CASE WHEN KPI Attainment % >= 0 AND KPI Attainment % < 25 THEN '0-24%' WHEN KPI Attainment % >= 25 KPI Attainment % < 50 THEN '25-49%' etc…

Hello. This was asked 2 weeks ago: The answer is no, and I recommended @deona720 add the idea to the ideas exchange. Not sure if that happened or not.

For data security no. You'd need to rebuild the integration.

Are you opposed to doing the join using Magic or SQL dataflow? Dataset views are notoriously buggy. Additionally would be impossible to troubleshoot without more information/screenshots/sample data.

Some ideas here: https://www.reddit.com/r/datasets/comments/9eiiv0/us_zip_codetime_zone_dataset/ You could also look at Domo Dimensions:

Is this how your rank is configured? It should definitely not be removing all rows of data. You could instead use the Group By tile and select MAX as the aggregation on Create Date. Keep in mind that you'll need to include all columns in step 1 that you want to remain in the data.

Honored! Huge thank you to @AnnaYardley , @sierrawise and @GrantStowell for all of your support!

@DanBrinton ^

Using filter views is a good option with PDP for strict restriction:

Not without a custom DDX brick. However, you could use hover text for the values and the series as the data label default. So you'd see hte view you screenshot above and then on hover you'd see the values.

Yep! Chart Properties > Data label settings > Text = %_SERIES_NAME > Show On: Last Item Only

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".