This depends entirely on your business period. There are many ways to achieve this here is an example which supports one where we lookup from the business data itself. Ideally you need a lookup table in your database which looks like this: YYYYMM Well you are in luck as this blog will share all. When running automation sometimes its easier if you can delete the data of the current period and replace it with the fresh data from this period. There are many ways to do this and I have kept this example simple to follow along, but for some organisations dates and times don’t follow monthly patters and cannot simply use MONTH() or YEAR() functions they have to build it on 4 weekly patterns or even 3. This first one is about having a lookup table within your database of the current business period and the previous one and why that is useful when data engineering with Alteryx and Alteryx Server. So this mini series is for me to put pen to paper and share those useful tips with you all. Starting fresh with Alteryx Server and Designer within a new organisation reminded me of all the small useful things which I had set up that I took for granted. Welcome to the Alteryx Automation mini series on Intersections and Overlaps. Alteryx Automation Series: PreSQL in Output Tools
0 Comments
Leave a Reply. |