Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
I am looking to report out lifecycle history event timestamps against Part Requests. I've done this with other objects but in this case, Part Request is iterated so those events are occurring against difference object iterations.
The QML from CS420621 is a method I've used before where you linked to the object history and filter by state. To get them into columns, I believe I needed to create multiple calls to lifecycle history:
Now, in some cases the Part Request might not have an phase for that state, so I would expect nulls and having to use outer joins. Despite my best efforts, Query Builder seems to opt to just filter those out (only showing ones that had all states).
To deal with the multiple iterations, I added criteria to link on the master id:
What should be hundreds of rows, drops to a few dozen. So easy to handle this in SQL. Any obvious mistakes or other things to try? Goal is to list events in the same row, one row for each request. If there was no event for that state, it should report nothing, null.
If there was no event for that state, it should report nothing, null.
From my experience with Query Builder, anytime you say IF / THEN, it's going to really hard to build in Query Builder, if not impossible.