GrantSmith Coach

So are you just looking to see if the most recent file received date comes after the encounter date for each patient?

There's been a few more fixes which have been pushed out. If you're still having the issue I'd recommend logging a ticket with Support about the issue.

What you might need to do is query your dataset to see what transaction dates were updated during the last partition chunk of insertion date and then re-pull the all of the transactions with the transaction dates from the list of transactions dates which were inserted / updated. So you're partitioning based off the…

Using a partition connection will allow you to pull in a subset of the data that gets updated instead of having to pull all of the data which would reduce the amount of data needed to process and thus improving the import speed into Domo.

I'd recommend reaching out to Domo Support as this sounds like a visualization bug that the development team might need to take a look at.

Are you sorting first on the unaggregated date filed and then sorting on the unaggregated sort order beast mode you wrote?

You can use a Group By tile in your ETL for each encounter date and location to get the min or max date instead of making it a comma separated list of strings. You can then compare to the maximum date instead of all the dates. You'll need to join your group back to your original dataset based on your grouping fields to put…

This example was deployed to the domo-dojo instance for reference. https://domo-dojo.domo.com/page/1880852133 If you need access you can refer to https://dojo.domo.com/main/discussion/55204/access-to-domo-dojo-instance

You'll want to make sure you have all of the data for the month for each update as it's going to replace the old version of the month data. Instead of joining on a date you'll want to calculate the month (you can use YEAR and MONTH to calculate it or just LAST_DAY on your date to get the month date) and join on that month…

What I'd recommend is establishing a new date dimension dataset which has each of your fiscal week values for each of the dates, you can then join this to your dataset to have the correct fiscal week number

Have you looked into the new Variables that Domo just deployed to dynamically change your values? https://domohelp.domo.com/hc/en-us/articles/7903767835031-Variables-Overview

The batch_last_run will be the value when your raw data is imported into the system, the currentdate in an ETL would be populated when the ETL actually runs. Depends on what you're wanting to track with your date.

You could use it as your partition key but if you're only wanting a single entry you'll want to convert it to a date first before using it as your partition key.

Use a group by tile to group on the name / ID and then take the maximum of your date field.

Currently it's not an option until they allow group ownership of datasets. You could utilize an email address that would then forward emails to a group but that would have to be handled in your email server outside of Domo.

Are you using RANK in a window function? It sounds like you don't want any missing numbers in your sequence. Rank will ignore numbers if there are ties in your dataset. In this case you might want to try DENSE_RANK instead as that won't have any skipped rank numbers.

Hi @SLam I'd recommend reformatting your data with a date offset dimension dataset and using a beast mode to calculate the different between last year and this year. I've written about this before here: https://dojo.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest You can then…

It doesn't appear Domo has a connector already written for CMiC but you could write your own custom connector to pull the data in. You can get more information by https://developer.domo.com on creating your own custom connector. Alternatively you could use a Python script to communicate with the API outside of Domo and…

Currently there isn't a simple way to do this and it must be done manually.

It sounds like your data might actually not be null but an empty string. Try something like this to handle empty strings and strings with just spaces: WHEN COALESCE(TRIM(`Building Status`), '') = '' THEN 'XYX' coalesce returns the first non-null value in the parameters supplied. This forces null values to be an empty…

You can’t change how the data is displayed conditionally based on the type of chart selected. You can graph it as a bar chart and by default it will display the raw data table when the user clicks on the card in the details view.

There isn’t a way to switch the color on a single line however I’ve used two lines with the same values and a beast mode to conditionally display certain values. You’d use your metric as the weekday which would display the weekend and weekdays. CASE WHEN WEEKDAY(`Date`) IN (1,7) then `Metric` END you’ll have to play around…

Use the LIKE command instead of <>

Currently this isn't an option as you're only able to drill with both values being filtered. I'd recommend adding this as an idea under the idea exchange section of the Dojo so the product team can utilize your feedback for their roadmap and to allow others to vote for this idea.

There are perks for having something as a beast mode and perks for having something in an ETL. If something needs to be recalculated on the fly utilizing a filter then I'll go with a beast mode. Most of the time I'll try and put calculations into the Magic ETL so that the processing may take a fraction longer to prepare…

You can try and utilize the General - Fill Empty Data Cells with 0 settings on your pivot table to fill the blanks with a 0 and then try and compare to 0 for your color rule.

The user who you authenticated workbench with is the owner and must either share the dataset with you or make you the new owner for you to see the dataset.

No Sumo cards are still used and can load more data easier than the pivot table but the don’t have as many features. Also Sumo tables are how you can read encrypted data. That’s not possibly with the pivot table. Short answer is that sumo tables are still around and have uses.

When indexing you typically want to look at the combinations of fields being used within your joins. This will allow the join to look up the data faster to be more performant.

Pydomo doesn't support setting/uploading profile images. You could monitor the network traffic to determine what the API call it's making to then replicate in your python script with a package list requests. I had done this in the past but can't find the endpoint. You will need to make sure you set the Content-Type…