list item duplicates values based on when new email arrives based on subject values

[Veblitz]

When new email arrives im extracting subject values and storing it in the list item 

Incoming email sample

Subject:USA,Client9

So if they are using same subject values but different attachments then it should update document library for the new attachment but at list item level it should not create new item as per below, so how to prevent duplicity in this context.

Flow details

How to prevent duplicates in the list item and in my case if the subject has same values then how to restrict those items 

set country variable expression:

last(split(outputs('Compose')[0],': '))

set customer variable expression:

last(split(outputs('Compose')[1],': '))

[Pstork1]

If you don't want duplicates then you need to use Update Item to update the existing item instead of Create item to create a new one. So you need to check the subject against all the items to see if one matches before doing either the Create Item or Update Item.

[ManishSolanki · Accepted solution]

Hi @Veblitz 

Use "Get items" before "Create item" action, apply filter query in get items to check if item with customer & country already exists in it. You need to use odata query for both columns i.e. country & customer.

Add "Condition" action to check the length of output array return by "Get items" action using an expression. If output contains any element then update item else if output is empty then create item.

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

[Veblitz]

As per my above flow steps this is the complete flow details and i added get items as per your inputs and tested by sending same email subject but different attachments but in my flow duplicate items were not added which is correct but at the same time email attachment is different and that is skipped and so in my case its working No condition.so what i mean is that in my flow it work partially though your inputs were perfect but im not aware where to place get item actions logically in order to skip through this new issue where different attachment for the same email subject is ignored.

Kindly advise

[Veblitz]

I tried but no luck,

here is my flow run history

[ManishSolanki · Accepted solution]

Hi,

In no branch, you may compare the email attachments with attachment present in output of "Get items" action. Use "Get attachments" action from SharePoint connect and compare its name with attachment name in condition action. You need to use nested loop to perform the comparison. Use string or array variable to store the comparison result for each attachment. Post comparing, check string or array variable value and accordingly save attachment or email in document library.

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

[Veblitz]

Okay.

I will try the same but I'm not sure if I understood fully and what I mean partially is that how to use expressions inorder to compare get items attachments and get attachments actions values into an array variable .kindly shed some light.

[ManishSolanki · Accepted solution]

Hi,

Here is a sample flow to check if email attachments are stored in document library. If attachment does not exist in document library, then flow will add it there. Please modify it as per your need.

In this example, I have a document library 'Test Library' and there are two files added in the nested folders:

I have taken static folder path in compose action but in your case it should be dynamically created:

/Test Library/2024/Jul/USA/Client9

Next, add "Apply to each" action to iterate email attachments. Pass the attachment array object from the output of trigger:

Add "Get files" action inside "Apply to each" block to check if attachment already exists. Pass the output of compose action in 'Limit Entries to Folder' parameter:

Use below filter query to check if file name exists in customer folder path. Just copy & paste in the filter query textbox:

FileLeafRef eq '@{items('Apply_to_each')?['name']}'

Now, add "Condition" action to check the length of array return by "Get files" action. Use expression to check the length of output array from previous action:

length(outputs('Get_files_(properties_only)')?['body/value'])

If no file is found then create new file in "Yes" branch. Pass dynamically folder path where file needs to be created. Pass the attachment name & content from the attachment array object:

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

[Veblitz]

Thanks a lot for your awesome support and detailed information. Fantastic.