I have a problem statement in which I have to export the updates in list items. Here is a scenario to picture the problem:- I have 6-10 lists in my model and each list has 6-15 members. Let's say, user updates a list item in one of the list then I want to export this information that which list item was renamed / added / deleted with its list name.
Anyway to be able to see changes you need some king of "before/after" comparison somewhere. You can setup an API process to extract all the info from all of the lists (i.e. via saved view of attribute modules). And when run the API job - you compare this export with the previous one to see what has changed. Make it automated. Or you can build a process in the model. The same idea. All the info collected in some storage for later to be able to compare it with new edits.
@ShubhamCh What you want to achieve it's a bit more complex if you want it to be working for re-naming and deletion of list items. But should be doable.
1. Create a second identical list that includes all list items with identical code names/numbering.
2. Create a property "original item" in second list (list formatted) and create an import action from original list to "copy list" and map by code.
3. create two modules where you will apply each of the two lists: (one will help you see renamed and deleted) and the other will help you see added list items.
Module 1: (applies to your copy/fake list)
Create line items: line item name /code / original line item name / original line item code - you can then compare the names of the two lists - where false, that means you've changed the name in your original list. Where blank (original name & original code) - it means list item doesn't exist anymore.
Module 2 - do the same thing - only this time blanks represent the the line items that were added in the list. Here you'll probably need similar approach to step 2(only the other way round).
4. Create exceptions views that you can apply to a dashboard or create export actions to only download the changes.
This will only work if you have clear timeframes for when you will perform the checks. At some point you need to clear and import everything from original to copy/fake list - at the beginning of each day/week, someone need to run the process so that the two are in sync.
1. Why would you use a list Item when we just need a boolean which tells us if the export is required or not? 2. Why would you use list properties to keep this data when any data can be easily kept in a system module? Let me know if I'm missing anything
@ashubham I don't see how you could keep track of the deleted items without keeping a copy of the original list. Yes, you will be using a Boolean to tell you if the export is required, but you need to compare both ways. Agree, List properties can be kept in a sys module, it's my recommendation also, but for this exercise it was faster for me to showcase the example.