Building flow from a SharePoint list to a create a CSV file

(0) Share

Report

Posted on by cmacdonald

Hi all. Wondering if anyone would know how to help me on this one.

I have an SharePoint list where I input Employee information, Name, User ID, Hire date etc...

I have built an automated cloud flow that gets triggered when new employee information is entered on this list, and stores the information onto a CSV file in a document library, then emails that CSV files to people.

Currently, ALL of the data on the SharePoint list gets added to the CSV file, I only want NEW data to to appear on the CSV file.

I have tried multiple conditions, but none seem to work, I think what I need is one that is: Created by is equal to "Todays Date"

does anyone know how to do this? I cant seem to find an expression that matches exactly

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (2)

nitishsh91 200 on at

Like (1)

Report

Hi @cmacdonald

You can use the "Filter array" action to filter the SharePoint list items based on the "Created" date field. The "Filter array" action takes two inputs: the array to be filtered and the condition to filter by. The condition is an expression that evaluates to true or false for each item in the array.

Here is an example of how you can use the "Filter array" action to filter the SharePoint list items based on the "Created" date field:

First, you will need to retrieve the SharePoint list items using the "Get items" action.

Next, add a "Filter array" action and connect it to the output of the "Get items" action.

In the "Filter array" action, set the "From" field to the output of the "Get items" action.

In the "Filter array" action, set the "Filter Query" field to the following expression:
Created eq '{{utcNow()}}'

This will filter the SharePoint list items to only include items that have been created on the same day as the flow is running.

Next, you can use the "Create CSV table" action to create a CSV file from the filtered SharePoint list items.

Finally, you can use the "Send an email" action to email the CSV file to the desired recipients.

Note: If you are using SharePoint online, you can also use the OData filter query to filter the items based on date, like ?$filter=Created eq '2022-12-01T05:00:00Z'

It is important to note that the above solution assumes that the "Created" date field is being used to store the date when the list item was created. If your SharePoint list is using a different field to store this information, you will need to adjust the expression accordingly.

Was this reply helpful? Yes No
cmacdonald 25 on at

Like (0)

Report

Thanks. That still gave me everything in the SP list.
This is what I have in as the flow

Was this reply helpful? Yes No
Verified answer

nitishsh91 200 on at

Like (0)

Report

It looks like you are using the "Get Items" action to retrieve all items from the SharePoint list, and then using the "Filter array" action to filter out items that are not equal to today's date.
Instead, you can use the "Filter query" option in the "Get items" action to filter the items that are retrieved from the list. This way, you are only retrieving the items that you need, and you don't have to filter them out afterwards.
In the "Get items" action, change the "Filter query" to: Created eq '{utcnow('yyyy-MM-dd')}'
This will filter the SharePoint list items to only include those that have been created today, and the rest of your flow will be using only those new items.
Also make sure you're using the correct date format based on the date format in your SharePoint list.

Was this reply helpful? Yes No
grantjenkins 11,063 Moderator on at

Like (1)

Report
@cmacdonald Are you sending the CSV file out daily with all items created say in the last 24 hours, or something like that? If that's what you're after, then this is how I'd build the flow.

Note that if there haven't been any items created in the last 24 hours, then it could just not send an email, or still send an email saying no new items created today (up to you on what you would want to do in that instance). In my example, I don't send an email unless there is at least one new item.

For this example, I'm using the following list.

See full flow below. I'll go into each of the actions.

Recurrence will trigger my flow every day at 8AM. You can set whatever suits your requirements.

Get items will retrieve my list items, but only the items that were created in the last 24 hours. Since our Created field contains both the date and the time the item was created, we need to use an expression to check between two date/times. The expression used for the Filter Query here is below. It checks if the items were created after 1 day ago, and before the current date/time - so in the last 24 hours.
//You can just copy/paste this directly into the Filter Query box Created ge '@{addDays(utcNow(), -1)}' and Created lt '@{utcNow()}'

Condition checks to see if any items were returned (any items were created in the last 24 hours). We use the length expression to check the length of items returned. If the length is greater than 0 then we know at least one item was created, so we can build our CSV table and send the email. The expression used in the condition is:
length(outputs('Get_items')?['body/value'])

If the condition was true, we go into the Yes branch.

Create CSV table uses the output from Get items and maps the fields we want to include in our CSV table.

Send an email will send an email with the CSV table attached. Note that we also need to include a name for the CSV including the file extension. In my example, I've called it Records.csv.

After running the flow, we would end up with an email similar to the one shown below.

Note - if you wanted to send a different email when no items were created in the last 24 hours, you could add another Send an email action within the No branch that said no new items, or similar.

----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
cmacdonald 25 on at

Like (0)

Report

@grantjenkins that worked. Thanks. One other question. how would i write the filter query to give me entries that were created only today? not 1 day ago until today

Was this reply helpful? Yes No
Verified answer

grantjenkins 11,063 Moderator on at

Like (2)

Report
You can use the following expression where it gets the start of the current day, and the start of tomorrow, then checks if the date is between those two dates.

Created ge '@{startOfDay(utcNow())}' and Created lt '@{startOfDay(addDays(utcNow(), 1))}'

However, in this scenario you need to be aware that if you run the flow at 6PM each day you may miss items. It will only retrieve the items created up until 6PM each day, so when it runs the next day, it won't get any items that were created after 6PM (the last time the flow ran) since they were created the day before.

If you want to ensure you get all items created that day, you'd need to run your flow at the end of the day (just before midnight). I'd still suggest just getting items created in the last 24 hours, so you never miss any items.

Was this reply helpful? Yes No