GrantSmith Coach

You could potentially use two variables and a beast mode to calculate the difference between your two values however there isn't a way to automatically populate these values in the variable so you'd need to manually enter them. Alternatively you can do a giant cross product of your dataset such that you have the data…

Hi @Byboth Typically if a Domo connector doesn't get me all the information I need I'll either write my own custom connector or utilize python, the pydomo package and the associated platform's API SDK packages to pull the information I need. This gives me more control over how I pull and process the data.

Yeah, it should be a date field to return the proper year. If Org Creation is already the year then you can just remove the YEAR() function in the beast mode

The slicer will filter your dataset if the field being used on the slicer exists in your dataset. As long as your subset dataset have the same field name that you're filtering it should work for you.

You can use the TRIM function in a formula tile to strip leading and trailing whitespace off of a string.

You're correct, Minimum isn't an option, apologies. I did log a new idea to the idea exchange to add this in as it seems to be a glaring omission from that tile: Really there isn't a way in Magic ETL except for doing a Group By and then joining back to your original dataset based on the grouping keys you used to get the…

Do you have any other firewalls in place or a spam server that might be filtering the emails? As @MichelleH and @MarkSnodgrass have mentioned it's typically a network issue that your IT team will need to get involved with as they can typically monitor the traffic and shed some more light on the missing emails.

Have you looked into using a Rank & Window til in your Magic ETL to get the minimum date across your column partition?

I haven't been able to successfully connect to AWS using those connectors as AWS requires some additional special headers for the connection. I'll use Python to write a script and use the Amazon boto3 package to do all of the authentications automatically for me. And then I'll use the pydomo package to upload data to my…

Ok, there's likely some other setting that's causing issues. Do you have any beast modes still on the card which reference a field that no longer exists? Are there empty color settings? If you right click on the page and select Inspect from the menu it will bring up the developer console, if you select the network tab and…

You can do this in a beast mode with a window function: SUM(COUNT(`fieldtocount`)) OVER (ORDER BY YEAR(`yourdatefield`))

You need to aggregate the aggregate when using a window function in a beast mode because of how Domo processes the beast mode. You could do something like: COUNT(MAX(`ID`)) OVER (PARTITION BY `Clinic`, `Product`)

You can select a specific sheet when you're uploading a file to Domo if it's an Excel spreadsheet and then have multiple datasets for your different sheets and then use those different datasets in your ETL.

If you want to add users in bulk you can do that using a CSV and also have a value to toggle sending the welcome email or not: You can specify TRUE or FALSE for the sendInvite value in your CSV to send the email or not.

You may be able to automate sending an email and using the Dataset via Email connector - See Alternatively, if you want to be more technical you may be able to write a custom connector and leverage SSRS's REST APIs:

Currently no, this isn't an option but It'd be a great recommendation for the Ideas Exchange.

This won't work in a beast mode as you can't aggregate (sum of total per reason) an aggregate (total per reason). You'd need to pre-aggregate the data in an ETL first and then do your final grouping in the card.

@user07231 Are you getting any sort of error message with the SQL Partitions connector? How exactly are they not working correctly?

I'd recommend adding this to the idea exchange for the product team to review and possibly re-add back into the product. It will also give visibility to other users and allow them to add their voice to this issue.

Which version of python are you using locally and which version is your script using? import sys print(sys.version) Is it giving you a line number which is causing the error?

You should restructure your data so that it's stacked so you have one row per observation (sales or service) Unit ID | Date | Date Type 1 | 1-Jan | Sales 2 | 2-Jan | Sales 2 | 2-Feb | Service Then use some beast modes to count your sales and service units: COUNT(CASE WHEN `Date Type` = 'Sales' THEN `Unit ID` ID END)…

@Utz Can you give me some sample data of your existing dataset, the dataset changed and what the final snapshot dataset should look like?

@Utz It sounds like you just want to take your old historical dataset, add your new data to the old dataset with the timestamp? In that case using a Magic ETL start by just having your original dataset as an input, feed it into a formula tile to add the snapshot timestamp and then output it to a new dataset. Save and run…

Not with the default visualizations. You could try and utilize a third party visualization tool like D3 in a Domo Brick to truly customize a scatter plot how you're wanting it displaued.

Custom Domo Connectors are written in the ES5 version of JavaScript.

You wouldn't necessarily need to create separate connectors but define different reports within your connector to allow users to select and handle those selections in your code to call the correct endpoint.

There's three steps to configuring GraphQL Describe your data (schema) Ask for what you want (query) Process your data Underneath the hood GraphQL is just like another API where you format a request, send your request and then process the data you get back from that request. The only difference is that you're defining what…

Have you thought about restructuring your data so that each record is a type of go-live? ID | Go Live Number | Actual Go-Live | Initial Go-Live Then you can filter on the Actual Go-lIve date value for 2023 or use the date filter for this year and perform a date diff between actual and initial to see if it's an on-time.…

Are you wanting tick labels or just a generic x and y label? If you're looking to just put some text on the axis to state what the units or metric you're displaying is you can just add a new text feature. x-axis svg.append("text") .attr("class", "x label") .attr("text-anchor", "end") .attr("x", width) .attr("y", height -…

Are the columns the same data type? Do you have extra / trailing whitespace in the column names? Domo should recognize them as one column if they're named exactly the same.