ArborRose Coach

Here's a break down of the way I was thinking. Apologies my docking unit just died and I have no monitors. I'm not used to using a laptop screen…lol.. AppointmentID,AppointmentDate,Provider,Metric 1,2024-06-15,Mitch,1 2,2024-07-20,Justin,1 3,2024-08-05,Kristin,1 4,2025-01-10,Kristin,1 5,2025-02-22,Kristin,1…

lol….Yeah, who's Brent? I don't see anything where you designate the % split across time. One way you could do this is to organize something to show the date duration and split %, maybe something like: Provider Galley Split % Start Date End Date Mitch John 100% 1900-01-01 9999-12-31 Justin John 100% 1900-01-01 9999-12-31…

Via Domo Governance Datasets you can find information about cards, pages, datasets, flows. However, governance metadata is more aligned toward dashboards/pages, datasets, and access, rather than specifically marking app to card linkage.

Thanks for the response Grant. In light of pydomo not supporting upsert - I rewrote my code to extract the existing data, combine it with new extracted data from the API, then remove duplicates and replace the data back to Domo. Due to the duration of Python run and credits consumed, I moved my testing to Visual Studio…

Lol…no. I can't stand using CLI and Jar files. I'd almost rather shoot myself in the toe and watch myself bleed out. Is that the only way to put a primary key on a dataset?

Yeah, that sounds buggy. Have you tried to create just a one or two entries using add columns? And then go back over and edit all?

I agree with Grant based on my experience with the Domo No Code Connector. This issue probably stems from changes on the Domo side—unless your IT team recently updated your network or proxy settings. Vendors usually don’t change their APIs often, but if the endpoint recently updated its authentication, request headers, or…

I don't think so. Beast mode can handle calculated fields but can't create a new total on a pivot table. They operate on row level, not summary. You can do the formula you show, but it won't add a separate total row in the pivot. Using Magic ETL you should be able to group by account, sum the MTD per account across regions…

Yes, I had that same problem and never got it to work properly.

Looks like your are aggregating inside the row logic. Domo re-evaluates the case when it calculates the Grand Total instead of summing the row results. I'd try creating two beast modes CASE WHEN `Revised Estimate (fixed by Estimate)` = 0 AND `Cost to Date (fixed by GL)` <> 0 THEN `Cost to Date (fixed by GL)` WHEN `Cost to…

I wish I had all the answers but I don't know the answer to your original question. Many things that could affect the issue. Also I don't do a lot of PDP. Possibly the user is a member of a group that has broader access. Possibly the conditions of your policy aren't filtering, ie the condition isn't truly restricting the…

PDP policies work the same in apps as they do in cards. See previous post:

See this previous post: Per Domo knowledge article, you can create a filter view and set it as default for every app viewer.

As far as I know, Domo does not support exploding the output - where each selection in your multi-select becomes its own row automatically. I believe there have been requests asking for this feature (turning multi-select selections into separate rows. Getting around that sounds tough. Like trying to pre-split on form…

As I mentioned, you could try to build out something that calls the Domo API. Maybe someone has code out there. In a brick or procode, I'd try something like: <button id="exportBtn">Download Dataset to Excel</button> With some kind of JavaScript or other code that looks something like this: import * as XLSX from "xlsx";…

Not really. Not in the way you are looking for. Domo’s native export options (Excel, CSV, PDF) are limited. You cannot control formatting, add dynamic headers/dates, or create multi-section, report-style layouts purely through Domo dashboards. Exported Excel files will be basic tables without merged cells, advanced…

Beast mode associates with the data used on the card, not the card or the page it rests on. It does not have access to the metadata about the page. And a card could be placed on more than one page. I have cards in Overview that are also on different dashboards. You might find workflow could help you. They give you more…

Congratulations on your certification! Safe space? The best? I am a potato. I put on a helmet and a seatbelt before entering the forum.

To duplicate that example, make sure you set your dataset0 to the sample products dataset. The code is referencing this as ${datasets[0]}.

Sure. You can do almost anything with a brick. Let's start with a basic brick to display a sample data file Here are the code parts: HTML: <main> <div id="result"></div> </main> JavaScript: var domo = window.domo; var datasets = window.datasets; // get the data domo.get(`data/v1/${datasets[0]}`).then(function(result){ var…

I don't see that behavior when I create a calendar selector. Throwing a sample dataset onto a calendar filter card, I see the following (below), which does not have lighter numbers for the current month. The best I could do was give you a reference to Domo's documentation. Does your instance have some kind of theme or…

Domo’s App theme can override certain card colors, including heatmaps in table cards. This happens because App themes attempt to enforce consistent branding, which includes a color palette. I don't think you can opt out except to use a brick or conditional formatting.

When you view a dataset, the id is shown in the URL. The wording dynamic sounds like you want to retrieve the id programmatically. Can you give a use case example for what you are trying to accomplish?

I would recommend you setup a workflow. Using AI you can probably come up with something more useful than alerts. If you haven't seen them, there are Domo recordings of recent community events where workflows are demonstrated with AI.

Here's the support page referring to colors on the calendar date selector:

You should be able to use a condition such as If % Planned < 70 OR % Planned > 95 And add the resource manager as a subscriber. If you need a guaranteed weekly digest (not just triggered when someone slips out of range), set up a weekly scheduled report of the same card.

Careful though—if you run it three times in a row while holding down Shift, you might accidentally summon a demon.

Sounds like Domo isn't supporting CAST / CONVERT in the dataset view. The dataset view isn't a true SQL view and Domo will still attempt to auto-infer data types. Can you force it by concatenating and empty string to it? CONCAT(column_name, '')

I think it's just a quirk that Domo needs to change/fix…design limitation. Try it as an icon and it should be visible. I believe it only does that on the navigation bar, not on pages. You can put buttons on the pages and they will stay visible. But on the nav bar, use an icon.

I believe Grant already answered this in a previous post. Check for upvotes on the idea exchange…if not found, post it.