We've recently made an accessibility improvement to the community and therefore posts without any content are no longer allowed. Please use the spoiler feature or add a short message in the message body in order to submit your weekly challenge.

Weekly Challenge

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!

Submit Feedback

Challenge #192: Crane Leasing

lucysinclair62
8 - Asteroid

My solution below:

Spoiler
lucysinclair62_0-1673975943560.png

 

BS_THE_ANALYST
13 - Pulsar

Generate Rows coming in to save the day

Spoiler
BS_THE_ANALYST_0-1674415628357.png

 

dougbaron
8 - Asteroid
Spoiler
dougbaron_0-1674873204294.png

 

StellaBon
10 - Fireball
Spoiler
StellaBon_0-1675446430400.png

 

Good practice for generate rows using dates

caltang
11 - Bolide

Got it done!

 

Spoiler
caltang_0-1675659175293.png

 

François_Rs
8 - Asteroid
Spoiler
Spoiler
Franois_Rs_0-1675941174830.png

 

Ed2000
8 - Asteroid
Spoiler
Ed2000_0-1676044311116.png

 

subhajit843
8 - Asteroid

Here it is

BSilverblatt
8 - Asteroid

Thanks for the challenge! Here's my solution:

Shahbaz_analyst
8 - Asteroid
Spoiler
Shahbaz_analyst_0-1677768389800.png

 

Interesting thing I learnt about the generate rows tool in this challenge. If your newly created field is a datetime type and your end date field is just a date type the generated rows won't include the last date even if your expression says new field <= end date field. I assume this is to do with the time component not lining up with the end date but it took me a while to figure out why I was getting different amounts of rows using the generate rows function when i updated a field vs creating a new field.