jaeW_at_Onyx Coach

yes. calculate the length of your string. then subtract the length of your string if you replace the search character with a blank. ex. length('mf_string') - length(replace( 'mf_string', 'M', ''))

 A table card might be an effective way of displaying a grip of metris succinctly alternatively the Spark Lines card can also show a densely packed set of metrics.

agree with @WHM 's commment... there really isn't a strong reason to export a million rows of data at a time... if you're trying to export your data mart for the sake of backing up your data mart in the JavaCLI there are tools explicitly designed for this task (save to S3 for example). also there are tools like writeback…

You can't build a CASE statement on your Aggregate in Analyzer / Beast modes even with the Beta feature @GrantSmith is referring to. Said beta feature ("Filter on Aggregates") will allow you to ... filter on aggregates, but it won't solve the problem of wanting to bucket activities based on an aggregate. This is a well…

To add a little nuance to it all. PDP policies control what an individual sees when they go to a dataset. Sharing a dataset allows a user to know that an asset exists in Domo. So ... when you share an asset with Group C you don't have to reshare with Groups A and B b/c you've already shared the asset. Additionally you…

In Domo you'll usually want to APPEND / UNION your data together not JOIN when you're combining transactions. Sales and Costs are a type of transaction. Alternatively you can think of Individual activity vs. Daily Total as different types of transactions. Either way, the answer is the same. UNION your data instead of…

@andres ... it's on the user to build the card that they want. i appreciate that the nuances of the differences between an HTML table card and a Megatable might not be clear.... but that's what the dev process is for. can you imagine being asked to document what features are supported in a pie chart versus features…

@user060355 ... be advised though... while showing the regression line in analyzer is interesting, it is very much dependent on the data that you see in your card. which of course implies, as soon as you add filters or interact w/ the card to apply filter, a new regression line will be calculated. it may make sense to…

http://www.silota.com/docs/recipes/sql-linear-regression.html @GrantSmith lol i'm half tempted to try to calculate this in a dataset view (which actually shouldn't be difficult) and then calculate the X and Y points as calculated fields in the DSV. Might have to build a view on a view... but then you could plot it as a…

if the datasets are of reasonable size you can do a cross apply on dataset A to dataset B (join where 1 = 1) then use a FILTER tile to remove rows that don't meet your JOIN criteria. It's not great, but it gets the job done.

you want to search multiple columns or the same column? b/c ATM you can defo use a filter card with checkboxes to many long text values. if you want to search across multiple columns you'd have to build a custom app for that b/c your app would have to 1) combine multpile columns / search across multiple sets of values,…

It's literally covered int the tutorial video ? you need to calculate rank in a dataset view (or ETL) then join it on to your activity.

@GrantSmith the user is describing an NPM package needed for building custom apps. not the java cli we're accustomed to using. @adrianiy have you tried installing validator? https://www.npmjs.com/package/validator

in order to use a connector. you must configure an account (credentials to that source system). THEN inside Domo, in order for another DOMO USER to refresh or rerun your SFDC (salesforce) connector, you must share the ACCOUNT with that USER. think about it. the account you use to access SFDC from Domo is functionally a…

You probably should not truncate your dataset. (unless we're getting into Billions of rows AND you're confident the data has no value.) Today you might not want that data, but in five weeks if you change your mind it'll be borderline impossible to recover the data you threw away without reloading it. I assume you're…

@GrantSmith is correct about the quotes and tildas. @tmullins is correct about the actual beast mode but has the incorrect quotes and tildas. CASE WHEN `PROVINCE_CD` IN ( 'BC' , 'AB' ) THEN 'WEST'ELSE 'EAST'END

could also write a script that generates a connector based on al ist of values in a CSV. but at that point why not sync Sharepoint with a local folder and then use workbench?

turn your visualziation into a table card and take everything off the axes except the beast mode. is it the same as the summary number?

Redshift dataflows can take anywhere from 0 to 15 minutes before it actually starts running. if you look at the details of the execution, you'll get a more accurate sense of the performance of your ETL once the data has been loaded into redshift. Similarly, after you run the etl the data has to be transferred back to Domo…

if the combination of row and column values don't exist, it won't show up in your pivot table. because your pivot table has no way of knowing that this combination of values 'should exist'. what you can do is UNION 'template' rows to your final dataset that includes each desired combination of rows/columns values, just…

to fill down data. for each column you want to track each time the row changes. so you need Prev_Value (use a LAG 1) then is_Change (case when Prev_Value != value then 1 then 0 then cum_sum of isChange in your previous example you should have 1 all the way from Text 1 to Text 2, then from Text 2 onward should be a 2 up…

do you HAVE to have it in ETL? b/c you could shape your data by creating a Date Dimension with two columns Report Date and Activity Date, such that the report date has A Day, and for each day in the Report Date you trail 50 days. So if my Date table had 5 consecutive ReportDates, it'd have 5 * 50 (trailing) Activity dates.…

https://www.youtube.com/watch?v=PVbOeLSae9o&t=748s don't JOIN your data in ETL in any fashion. Instead, STACK the data using APPEND as demonstrated in this tutorial. If you JOIN in ETL and aggregate you limit your ability to filter. If you go the opposite direction and duplicate rows, you have to do 'crazy math' to…

... if you google both "cumulative sum domo" and "running total domo" there are solutions that immediately pop up. is there something specific that stops those solutions from being applicable? https://www.youtube.com/watch?v=ZPf41Fjn1H8 // how to calculate cumulative sum. https://www.youtube.com/watch?v=cnc6gMKZ9R8 // how…

If you're using a pivot table with months on the axis, your data set is no longer 3 rows, it'll be around 3(categories) * 12(months) assuming you have data in each month... in other words, it gets weird. so don't use a pivot table if you want to limit rows that way. instead build a beast mode for each month.

are you sure the Oppty isn't being ingested into domo? have you validated that the opty is missing (by filtering on the SF object id? or are you filtering to where 'type' = null. b/c filtering on NULL in analyzer can be a bit weird.

https://www.youtube.com/watch?v=39VHAQEYHAc&t=220s Covered that requirement in this use video

Take a look at Zapier.com Here's a tutorial going the opposite direction, but the concepts are similar https://www.youtube.com/watch?v=YOaOzpXGtbo

here's a pretty extensive tutorial on window functions. https://www.youtube.com/watch?v=eifSYZIcPzg you can't filter on a rank in window functions. but you can set the data row limit to 2 or 5 or 10 rows and sort by sum(Amount) desc which is functionally the same thing. in your case if you have months on an axis, to get…

you can't filter on AGGREGATE FUNCTIONS (like SUM() or COUNT()) in beast modes without a feature switch. you can filter on non aggregate functions like CASE or IFNULL.