Best Of
Re: DOMO Tag report
@A_Benincasa Here is an example of what this would look like. I actually used the "Dataset Details" report from the Domo Governance Connector instead of the DomoStats connector since it already includes the Owner Name instead of just the Owner ID. Note that if you want to only include datasets with the "Delete" tag in your final output you can change the Join Type from "Left Outer" to "Inner".
Re: Execution order of AND/OR in case when statement
- (A AND B ) OR (A AND C) should work for what you want to achieve, as will your case statement with multiple conditions. Grouping different conditions using parenthesis is generally best practice if you are using just one line to avoid ambiguity.
- We need a little more information about what rows your want to include to be able to point you in the right direction
If you're ever unsure about how rows are being classified in case statements, I find that it's helpful to test multiple beast modes in a table card to see how each row is classified.
Re: Keeping only the latest date for unique ID
Another option is to use the Group By tile and choose Max for the aggregation type on the date field.
Re: Keeping only the latest date for unique ID
You would use a rank & window tile in Magic ETL. You would rank your data on date in descending order partitioned by the ID field. You would then use a filter tile to only keep rows where rank = 1.
If you get stuck let me know!
Re: Ability to turn off the "REQUEST MORE ACCESS" button for Social users
I agree with this. Generally we give social logins because there is a reason we don't want them to have full access. If someone needs a full license that request is handled through other channels, so we don't have a need for this button.