jaeW_at_Onyx Coach

you may have to use a different chart type (chart / line) or bullet chart, but then just create a beast mode with the current date, a series, and a value. yeah... that's ugly. you could use a data label with a custom value (setup a beast mode) that's only populated on the current date. I've had clients change the chart…

i do not know 100% but would not be surprised / it would make sense. APIs wouldn't want to stream billion row datasets to you. instead it would be secure (in case of network interruption) to send data in n-sized row chunks. so ... yeah.. makes sense. in a similar way, i would not read the data directly into a pandas…

given that you have a graph, it's unclear to me what you do and don't have done. that said a few things to consider. 1) ignore fiscal year. or fiscal week. as i understand it, your question has nothing to do with a calendar year, it's just "did behavior change before and after training." that's irrespective of time of year…

i know this isn't the answer to your question. but consider using a different visualization. if the slice of the pie is so small that the UI doesn't render a label, it will probably be very difficult of a user to clock the difference between group 1 and group 2. at most, they'll think "oh... that's a huge difference."…

can you be specific about what's not working?

just FYI i believe that mathematical operation is called "Modulo" or "Modulus" https://www.w3schools.com/sql/func_mysql_mod.asp https://docs.microsoft.com/en-us/sql/t-sql/language-elements/modulo-transact-sql?view=sql-server-ver15 @GrantSmith i noticed you wrapped in Round , 0 to get rid of trailing decimal places. I guess…

to the original poster / @MichelleH and @Ashleigh , the design of the dataset was flawed which is why the user struggled to solve their problem. "Operational Places" is grouped by "ACPR Name" and "Organisation Type". "Number of Clients" is grouped only by "ACPR Name" in a different ETL, hence why the numbers are the same…

it might benefit you to start a new thread b/c it's unclear if your problems are actually related to the initial issue. either way. definitely do not make 100s of beast modes! that would be such a PITA to maintain. if you have multiple "Types" in one column, experiment with putting Types in "Series" or "Categories". Also,…

contact your CSM. this is a beta feature in development.

you mean other than the KB articles?Which grants you give will have a lot to do with how you structure your domo implementation. how do you plan to segment people. how will you handle inter and intra departmental data? who will be building content? who will primarily be consuming content? Focus on what adoption and rollout…

it is unlikely that the data from mixpanel is presented in the original way that it was stored in the database. keep in mind when you extract data from mixpanel it's being sent as a JSON object which by definition means that it can contain data stored in a non relational format (instead of single value fields, a JSON key…

just convert your column to Numeric then back to text and take a LEFT 1.

Instead of aggregating the data with a SUM() I would simply UNION the data on top of itself, and then assign a hard coded value of "Rep Owned" to the first copy of the data in the column that usually contains "Accept" or "Converted". THAT said, assuming you're working with salesforce or similar data that tracks…

you won't see the schema in the Domo UI until you load data.

 in table cards you can use HTML + CSS to display images (or format text) https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Transforming_Data_Using_Beast_Mode/Adding_Graphics%2C_Links%2C_and_Images_to_Table_Cards_Using_Beast_Mode

You haven't stated what's going wrong in your code ... maybe try wrapping date in a MAX() function 

Instead of uploading an excel spreadsheet, i'd use a Webform because then I can alter the values as necessary inside the Domo UI. Instead of JOINING in ETL, I'd use a Fusion to LEFT JOIN the data. By using a Fusion you don't have to wait to reprocess the data if you want to add a new filter criteria. It'll be…

what's not working? can you be more specific about the errors you're encountering?

You'll probably have to work with support (or a consultant ? on this. but it sounds like your dataset had an UPSERT schema enabled. then you altered the schema or uploaded data and when it tried to reindex, it found a row that violated the unique-ness constraint which UPSERT requires. I would duplicate this dataset before…

be careful of using the term unique, in describing your problem. unless your data already is unique, if you don't include the unique operator in beast mode ... it won't calculate uniqueness. I point out this nitpick because you can't use SUM to calculate UNIQUEnes -- unless your data is specifically designed for it. That…

1) it would probably be easiest to perform server-side scripting that combines the data into one file BEFORE sending it to Domo. 2) most connectors have an option to Replace or Append data during ingestion to Domo (check if there's an option under "Scheduling" during connector configuration).

is this for a custom connector or a standard connector? if it's a custom connector, you can define your own scope. if it's for a standard connector, message support.

... i don't think you understood my last response to your last question. https://dojo.domo.com/t5/Beast-Mode-ETL-Dataflow/Case-within-case-in-beast-mode/m-p/50010 you have the same problem. you're applying AVERAGE to an aggregated row. SUM and a COUNT both of which will contain one row each. so your result will be the same…

Unless they made changes AFAIK pivot tables don't have support for HTML formatting. But let me know!

... i mean... if you think about it, it makes sense. You have a card filtered that SHOULD span two years. But then you filter to ONE year. So ... your card only has half the data available. It sound like you're trying to create a historical analysis (i.e. compare 2019 with 2018). Domo doesn't support that with the built in…

no not at the moment. Initially, filter cards were designed as a 'one or the other' regarding page filters. either use a page filter. Or use filter cards, but things get weird when you use both. the problem is, expectation. when you use filter cards, you intuitively know to uncheck the box that's filtering your other…

I don't think it's fair to describe the solution as poor. It just doesn't align with your expectations (i assume Excel.) Keep in mind that Domo visualizations and their entire approach to dashboarding initially was not designed to target Excel Jockeys, data scientists or analysts. The target consumer of a Domo dashboard is…

@GrantSmith is correct. but the larger question is, in what context do you care if there's a hard or soft delete? IF the issue is a question of GPDR compliance b/c a client requested 'the right to be forgotten' or whatever that verbiage is, yes, Domo is contractually obligated (AFAIK) to support requests like this. Usually…

It would be super cool to have a global study group for custom app work! I'd love to participate.

you would have to have a row for each department for each month. You can create a template dataset that has one row for each department with a fixed amount of 0, then UNION that to your actual dataset.