ColemenWilson Coach

Rename the 2 date fields, or create a new date field, in MagicETL to have the exact same name and then append the data from the two sources. Then you'll have a single date field and wont lose data when filtering.

If you are an instance admin then you control all grants. Grants are controlled in the Roles section in Admin settings. EDIT: oh I was able to replicate the issue you are having. Yikes that seems like a product enhancement need. I would suggest submitting this in the ideas exchange You can also modify the group using the…

If you leave the "Duplicate all cards" box unchecked, then changes to the cards themselves in analyzer will appear in those same cards in the other location. However, design changes to the page/app will not. Dashboard or app level changes will not affect the other content, but card changes in analyzer will.

For that you can use a nested beastmode: https://domo-support.domo.com/s/article/000005307?language=en_US Create a new beastmode that references your count distinct. AVG(その他の計算フィールド) Then select this new field as your summary number.

You would connect the data using the google sheets connector: https://domo-support.domo.com/s/article/360043436633?language=en_US Ensure that append is the proper update method for your data.…

You'll need to create a beastmode: COUNT(DISTINCT(あなたのフィールド) Then bring this newly created beastmode (calculated field) into your card in the y-axis spot. Here is a video on how to create beastmodes if you never have before: https://www.youtube.com/watch?v=SpVbmZPMAsM

It appears only when you hover next to the name of the furthest right group owner. You'll need the grant "Manage All Groups" to be able to edit closed groups owned by others.

The card wouldn't work with no value shown on that level of the sunburst. Logically there needs to be something there if there is an additional level. So for CEO you could have a repeated value of CEO, or N/A which makes sense because Level 2 doesn't apply to the CEO. It's just a limitation of the chart type. You could…

It can't handle nulls. For your next level just create a beastmode: IFNULL(`Level2`,'N/A')

I would create a bar chart. X-axis would be a beastmode: DAYNAME(date) 3 beastmodes would be 3 bars: 1. MAX(volume) 2. MIN(volume) 3.AVG(volume) I would also sort the bar chart using the following beastmode: CASE WHEN DAYNAME(date) = 'Sunday' THEN 1 WHEN DAYNAME(date) = 'Monday' THEN 2 WHEN DAYNAME(date) = 'Tuesday' THEN 3…

Yes, I would create a separate dataset that is for snapshotting purposes.

The easiest way to do this is to set the update method of your data to "Append" instead of "Replace". This way, each time the data updates, it is added to the dataset as an append so you maintain a full history. You can set this to run on a schedule (quarterly) but can also manually update the data anytime you please. For…

I don't think so, but that would be a question for the Lucid community! If so, it would be by creating an iframe and embedding that in Lucid somehow.

You won't want to use count distinct then. Can you share what your visualization looks like? If you have both Customer ID1 and Customer ID2 as fields in the table it will not work as you are expecting.

It would also be helpful to see what visualization you are trying to create and your expected view.

Beastmodes are case sensitive. I believe you just need to change 'Active' to 'ACTIVE'

This article is a great resource: https://domo-support.domo.com/s/article/360043437993?language=en_US If I understand your question correctly, you'll just need to check "Allow interactions and filtering" in the embed options:

It could have something to do with color rules saved to the dataset, although card rules override dataset color rules. But still something to check. Otherwise I would reach out to Domo Support.

It already has writeback functionality: https://domo-support.domo.com/s/topic/0TO5w000000ZapVGAS/writeback-connectors?language=en_US They will need to reach out to their CSM to get it enabled.

Interesting. The key consideration here is whether or not the PDP policies are configured properly. Is everything currently working as needed?

Not really sure I am following what the problem is. If PDP is not enabled on the data, you don't have to share the dashboard or dataset(s) with them for them to receive scheduled reports and see all data. If PDP is enabled, then you will need to add users to the PDP policies as you see fit.

Are you trying to stop them from receiving the scheduled report all together? If so, go MORE > ADMIN > Scheduled Reports > click the kebab icon (3 dots) > Edit Schedule > and then add or remove recipients

They do not need permission to the dashboard to see the scheduled report. But as you mentioned, if PDP is enabled for data used on the dashboard they will not see (or see a different view) of the cards powered by data with PDP enabled.

Where are you looking to see 3rd lowest day? In the dataset provided by Domo in the quickstart, I see the "date" field, which I assume is the date the credit was consumed/charged/whatever, but not necessarily when the 3rd lowest day of storage was.

There are a few connectors you could look at: JSON No Code Connector: https://domo-support.domo.com/s/article/360043433473 JSON Advanced Connector: https://domo-support.domo.com/s/article/360042932034

Similar to dashboards, you can only enable drill in place if a drill path has been created for the card. When importing a dashboard to an app, the drill path will come with it. If you did not have a drill path created before importing the dashboard, you will need to navigate to the card outside of the app and create a…

During the append, the matching fields being appended default to the most compatible data type between the appends sources. So if you change one source to Date, but the other is Date Time, it will change the data type to Date Time. You'll need to ensure that the data type for all inputs to your append are cast to Date. Add…

Edit App > Select the card > Actions > Drill In Place

Try: CONCAT(ROUND(Sum(CASE WHEN `To Step` = 'Forward to HM' THEN 1 ELSE 0 END)/(COUNT(DISTINCT `Requisition Number`)),2), ':', ROUND(Sum(CASE WHEN `To Step` = 'Hire' THEN 1 ELSE 0 END)/(COUNT(DISTINCT `Requisition Number`)),2))

You can wrap each of the two parts of your concat with ROUND(). CONCAT(ROUND(Sum(CASE WHEN To Step = 'Forward to HM'THEN 1 ELSE 0 END)/(COUNT(DISTINCT Requisition Number)),2) , ':', ROUND(Sum(CASE WHEN To Step = 'Hire'THEN 1 ELSE 0 END)/(COUNT(DISTINCT Requisition Number)),2) )