Best Of
Re: Workbench Schedule Jobs are not working .
Give your machine a reboot that typically solves problems I have with workbench.
Re: Workbench Schedule Jobs are not working .
@Ajita If you haven't already, try manually running the jobs to see if they are successful. If they still fail then I suggest the following:
- Verify that the Workbench user is still logged in. If that user recently had a changed or expired password, then you will need to re-authenticate in Workbench with the new credentials
- If your jobs use impersonation, check whether those credentials have changed as well
- Check that Workbench still has access to the data source and that the data has not moved or changed
Hopefully this points you in the right direction, but if you are still having issues feel free to share some Workbench logs from the failing jobs so we can look into it further.
Re: I need to convert a text column to date in ETL
If you have garbage data which doesn't match your date format ('Day' in your example) it may not be simple enough to just convert it to a date. You may need to conditionally set your date value:
CASE WHEN REGEXP_LIKE(`date_field`, '^\d{4}-\d{2}-\d{2}$') THEN
STR_TO_DATE(`date_field`, '%Y-%m-%d')
END
Re: Assigning Students to Various Organizations
@MarkSnodgrass Awesome solution! I immediately thought that this would have to be a loop in python but I love your non-python solution!
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.




