List

[Sanjana12]

Hi, there are two options:

1. Create a list using its own table

2. Purge and reuse the list if it exists

Can we call the first type of list a static list and the second one a dynamic list.

Note: I have observed the first one stores duplicate data as well.

[ParthaSarathy · Accepted solution]

Hi @Sanjana12 ,

If you want to create a list to use a schema other than the recipient table then check the Create or use a list with its own table option. Example, if you have broadLogRcp schema in query and to store the value in a list, you have to enable ' Create or use a list with its own table'

Whereas, If you enable 'Purge and reuse the list if it exists (otherwise add to the list)' option, each time the workflow runs it will delete the old records in the list and update the list with new values from the workflow. And If you disable the checkbox, then each time the workflow runs, new records will get inserted in the same list without deleting the old records.

[Sanjana12]

But can we call them static and dynamic lists?

[ALangridge]

Nah, they're all static - they're only updated if you run some sort of an activity to update the contents of the list. 

[Sanjana12]

Hi, if we check both the options in the list, are duplicate records going to get inserted into the list and deleted everytime we update the list?

[ParthaSarathy]

Hi @Sanjana12 ,

If you had selected 'Purge and reuse the list if it exists (otherwise add to the list)' option, each time the workflow runs - irrespective of new record or duplicate record, all the data from the list will get deleted first and the data from the workflow will get inserted into the same list.

[Sanjana12]

On the contrary, if we select the first option then unique records as well duplicate records will get inserted everytime the list is update.Correct me if I'm wrong.

[ParthaSarathy]

@Sanjana12 , Both options are for complete different use cases.

The first option 'Create or use a list with its own table' is not related to new or duplicate records. This option deal with schema perspective. If you enable this checkbox, you can create a list with any schema in your instance. If you disable the option, then you can only create list with nms:recipient schema by default. 

The second option  'Purge and reuse the list if it exists (otherwise add to the list)' - if you enable it, each time the workflow runs it will delete the old records in the list and update the list with new values from the workflow. And If you disable the checkbox, then each time the workflow runs, new records will get inserted in the same list without deleting the old records.