About zafkamar

Hi @geet.patel,   @rob_marshall's approach is a really good one.  See below for another approach you could take:   This is a really great opportunity to use the power of saved views and sorting.  What I would do to solve this problem is the following: In the module where you have your data (let's call it Module 1), sort your dates from "highest to lowest".  This will present the dates from latest date to earliest date. Click View -> Save As... to save the sorted view of the module as a Saved View. Create a new module (let's call it Module 2) dimensionalized by a UserID List and Line Items, where the line items are Plan, Subscription Start Date, and EndDate.  Make sure you format those correctly. On Module 2, click Data -> Import.  Import data from the Saved View of Module 1, making sure to configure the import correctly.  Most importantly, make sure to map the UserID text field from Module 1 into the UserID List in Module 2. When you import from the Saved View, only the first records of each UserID will make it into Module 2.  Since your saved view is sorted from latest to earliest, that means that only the latest records of each UserID will be brought into that module.   As always, there's loads more that you can do to make the process more efficient, but this is the basic premise.  See attached images for the results!   Hope this helps, Zaf ... View more

Hi Ryan,   An intriguing problem - this could be a job for the ISFIRSTOCCURRENCE() command.  What I would do to solve this one is the following: Create another boolean-formatted line item in the list called 'FO Product?' (our Lionpoint model builders like to use FO as an abbreviation for IsFirstOccurrence) using the below syntax: ISFIRSTOCCURRENCE('Product Code', Products) Create a filter on the 'FO Product?' line item -> this should result in a filtered list of transactions that only show the first instance of that product showing up... which should hopefully be when it was added. Save this filter as a Saved View, I'll call it "FO Product Adds > Transactions" Create another module called something like "FO Product Adds > Products" dimensionalized by your Products list and the same line items as your transactions module, especially including the Employee Number On the "FO Product Adds > Transactions" module, Import... Connect to Anaplan Model... Saved View ... "FO Product Adds > Transactions", and configure that appropriately.  Run the import. Once that executes, you should now have what you need to get the original employee who added the product.  On the original transactions module in the 'Employee ID who originally added' line item, you should be able to execute the following formula: 'FO Product Adds > Products'.'Employee Number' [LOOKUP: Product Code]  Hope that helps! -Zaf ... View more

Community is a cornerstone of getting really BIG ideas off the ground.  Thanks for all that you do! ... View more