How do I reflect team member on Team A before date and Team B after date.

I have a team member that has moved teams on a specific date. I need this person to be still reflected in Team A prior to 8/1/23 and also on Team B on and after 8/1/23. All other team members will remain in their current team.
Trying to use beast mode but getting an error. Any help would be appreciated.
case
when Date
>= '08/01/2023' and Team Member
in 'Name' then Team
= 'Team B'
when Date
< '08/01/2023' and Team Member
in 'Name' then Team
= 'Team A'
else Team
end
Best Answer
-
While this solves the particular case keep in mind that this solution is not easy to scale. I'd recommend using a Webform datasource to track Team changes with start and End Date, and then do some ETL to determine the team that person should be in for each entry based on it. Is more work, but that would allow you to have better control on this and can cover more complex scenarios should this be something that can happen in the future.
The Webform basically would have 3 columns:
Team Member Id
,Team
andJoinDate
, you could have aLeaveDate
but not mandatory as it'll be determined by the date of the next entry in the list via the same ETL and you wouldn't risk having gaps (of course this means you'll need to populate this the first time for all employees with their current value). Just an idea you might want to consider exploring in the future.1
Answers
-
I believe I figured it out…
case when
Date
>= '08/01/2023' andTeam Member
in ('Name') then (case whenTeam
in ('Team A') then 'Team B' elseTeam
end) elseTeam
end0 -
While this solves the particular case keep in mind that this solution is not easy to scale. I'd recommend using a Webform datasource to track Team changes with start and End Date, and then do some ETL to determine the team that person should be in for each entry based on it. Is more work, but that would allow you to have better control on this and can cover more complex scenarios should this be something that can happen in the future.
The Webform basically would have 3 columns:
Team Member Id
,Team
andJoinDate
, you could have aLeaveDate
but not mandatory as it'll be determined by the date of the next entry in the list via the same ETL and you wouldn't risk having gaps (of course this means you'll need to populate this the first time for all employees with their current value). Just an idea you might want to consider exploring in the future.1
Categories
- All Categories
- 1.1K Product Ideas
- 1.1K Ideas Exchange
- 1.2K Connect
- 970 Connectors
- 259 Workbench
- Cloud Amplifier
- 1 Federated
- 2.4K Transform
- 76 SQL DataFlows
- 502 Datasets
- 1.8K Magic ETL
- 2.7K Visualize
- 2.2K Charting
- 379 Beast Mode
- 21 Variables
- 487 Automate
- 104 Apps
- 379 APIs & Domo Developer
- 6 Workflows
- 22 Predict
- 6 Jupyter Workspaces
- 16 R & Python Tiles
- 319 Distribute
- 67 Domo Everywhere
- 252 Scheduled Reports
- 59 Manage
- 59 Governance & Security
- 1 Product Release Questions
- 5K Community Forums
- 37 Getting Started
- 23 Community Member Introductions
- 64 Community Announcements
- 4.8K Archive