community
cancel
Showing results for 
Search instead for 
Did you mean: 
Do you have the skills to make it to the top? Subscribe to our weekly challenges. Try your best to solve the problem, share your solution, and see how others tackled the same problem. We share our answer too.
Weekly Challenge
Do you have the skills to make it to the top? Subscribe to our weekly challenges. Try your best to solve the problem, share your solution, and see how others tackled the same problem. We share our answer too.
Unable to display your progress at this time. Please try again a little later, or contact an administrator if you continue to see this error.
Getting started with Designer? | Start your journey with our new Learning Path!

Challenge #80: Slowly Changing Dimensions

Meteoroid

Hereby my solution  

Asteroid

Can we expect to See Bob in the next generation of  Villains!?

 

Spoiler
RL_WK 80Solution.png
Alteryx Partner

My solution

 

Spoiler
challenge_80_RODO_Solution.png
Asteroid

PFA my solution

Alteryx Partner

Had a little trouble with the deletion of a person (I'm just too nice to randomly off someone).  I suspect that part could be more efficient.  But it works

 

Spoiler
Process
- Filter out person from Today's Updates if they do not have an End Date
- Union data together
- Sort by Start Datre
- Update End Date to equal any subsequent Start Date (to indicate a promotion)
- Current Flag reset to equal "N" if there is an End Date (i.e. there must be a new Start Date, so no longer current)
  -- Actually this leaves Bob's old data as showing as current - so this is less than ideal (even though I clean that up in the next steps), as it could create an error elsewhere in the workflow if not careful
- Union data with anyone filtered out in Today's Updatge
- Create a "Deleted" field if Current Flag is null
- Update "Deleted" field to all instances of that person
- Filter out Deleted records
- Cleanup and sort

MySolution.PNG