Doculabs has hard-earned knowledge about how Celonis works. As a Celonis partner and through our client work, we understand the ins and outs of Celonis process mining better than most.
To share what we know, we've created a series of videos. In this video, I break down how the Common Table works in Celonis. Once it clicks, it makes things a lot easier!
We can help your team take advantage of these tips -- and even find new ones!
You can watch the video and/or skip over to read the transcript.
Hi, my name is James Nman. Today I'm going to give you a short video about the Common Table in Celonis. What makes Celonis PQL (Process Query Language) so great is that it will automatically write the joins for you between different tables. Unlike SQL, where you have to write the joins yourself, Celonis will implicitly join tables together.
As an example, we're using our call center data, and the Common Table is described in the bottom right when you go into the edit of the formula. So, you can see the Common Table here is the event log table that's joined to the activity table.
The cases table is one relationship to the N rows of the event log. This will iterate if you do a case when, etc. As you see in the data model, it's a very simple data model. The cases table is automatically created and joined based on the case key. So, this is something to look out for if you only have your activity table defined.
Be on the lookout for the Common Table if you have numbers that don't match. If you have a formula in a number component that is working fine and then you put it into an OLAP table and it is no longer working, the common culprit, in our experience, is the Common Table having been changed. So, be on the lookout.
Happy programming.
Looking for more?
Head over to our ProcessMiningIQ community for even more tutorials and expert advice.
Commenti