Setting SharePoint ID - Slow

[Anonymous]

Hi All,

I have a flow which parse data from various API calls into a SharePoint list.

I want to be able to append changes to the items in this list - for example if an API call returns a statement that a setting has changed it would update the setting on this item rather than create a new item. 

I have in my flow therefore a Apply to Each with a condition that is if SharePoint ID is Greater than 0 set the SharePoint ID variable. Screenshot below. 

However, this seems to take 300% longer than if I delete all data from the list and let the flow enter the data each time. Example - fresh empty list flow takes 5-6 minutes. With data in and setting SharePoint ID the task takes 23-25 minutes and the total flow takes around 30 minutes to complete.  Am I adding the loop to the wrong place perhaps? 

Is there a more optimised way for me to set the SharePoint ID or indeed an alternative method to use some logic that goes along the lines of "If Item Exists then append, Else create"

Thanks in advance! 

@RezaDorrani  

[v-bacao-msft · Accepted solution]

Hi @Anonymous ,

You could consider using Filter array instead of Condition.

Like:

And increase the Degree of Parallelism to apply to each to improve the efficiency of execution.

Hope it helps.

Best Regards,

[Anonymous]

This worked really well thank you! 

[HelplessMax]

Hi everyone,

my question goes in a different direction, sorry if this is the wrong place for it:

Anyways i have two Sharepoint Lists:

List 1: items to be approved (Titel, ID ......)

List 2: items that have been approved

Whenever the item from List 1 has been approved it creates an element in List 2 but with a new ID.

Is there any way to carry the old ID to the new element?