Hello There!
I´m trying to create a flow that will remind users (Column Document Owner) of the documents that will expire within the next 30 days (Column Expiry Date).
I tried to build following this website (https://www.sharepointsiren.com/2018/03/using-flow-to-send-email-reminder-from-sharepoint-data/). I followed exactly.
The problems shows when the output is inserted: ExpDate eq ‘Output’
I removed this part, and the flow worked as charm (sending me e-mails of all itens within the List, without filter).
How can I solve this? Is the only thing that is avoiding me to complet my project task...
Error:
"status": 400,
"message": "Column 'ExpDate' does not exist. It may have been deleted by another user.\r\nclientRequestId: 9b63e1d6-6076-477b-aaa7-91756b3b61ac\r\nserviceRequestId: dfd6df9e-60cb-0000-b2f3-067f89e8dba9"
Solved! Go to Solution.
Please see my screen shot below.
In my example, Flow is referring to the column as ExpiryDate - if your output says Expiry_x0020_Date then use that.
Please note my date formatting: yyyy-MM-dd
Also, I did not use a compose action - there is no real reson to do so.
This is likely a syntax or formatting issue, so if you could provide an expanded screenshot of your Flow and steps, and of any detailed error messages you're receiving we could likely better assist you.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Brad, thank you for your fast answer! Hope you can help me solve it until the end of day!
I tried to upload images. Please check:
Overral:
Overral 2 (SCOPE):
Hi @Lucas_Goncalves ,
As the pic shown, the column name is 'Expiry Date'.
So you need set the Filter Query like below:
Best Regards,
Community Support Team _ Zhongys
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello!
Error persists!
Is the ExpiryDate column a calculated column? If so, that I believe that is your issue - you cannot reference calculated columns in an OData filter. To work around this issue, allow for the date calculation to take place in the compose action.
Hello!
Yes it is a calculated column!
It calculates 365 days after the Effective Date column:
Is it possible to show me how to manage to have this output? Maybe referencing EffectiveDate + 365 eq 'Output'?
Changed the column name (Effective date = column type is Date and Time); and same error:
The first step to resolving your issue is to see how Flow is referring to the column. Take a look at the output of Get Items without the Filter Query. Scroll through the output and see how your column is referenced. Flow usually, but not always uses the columns internal name.
Sorry could not understand...
Can you explain with images?
PS: I removed all Filter Query, and I receive an e-mail for each file, without filter. I mean, it is working. Just need to apply the filter to only send e-mail about those files that expired...
In the screen shot below, I have used the Gt Items action to retrieve items from a SharePoint list. In the body section of the output, I scrolled down to see how my columns are referred to. So, even though I have a column called "Another Date", it shows up in the output as "AnotherDate" (no space). In the Filter query, I would need to refer to the column as AnotherDate.
Ok, now it shows the error that effectiveDate is a calculated column.
How can I automate the flow that it must consider 365 days (one year) from Effective_x0020_Date?
PS: the real name of the calculated column was Expiry_x0020_Date! You partially solved my problem... now I need to find out how to automate this...
Can you tell me what calculation was being done in the calculated column? For example, was it something like Created Date plus 90 days or something like that? With that info, I can assisit you in creating your filter query.
Hello! I was thinking here... why I must have a "effective date", if Sharepoint already have a automated "created date" imput?
So I deleted the calculated form and changed column name to "Expiry Date" with normal imput for my users to tell sharepoint when it is expected to expire.
So new column name is: Expiry_x0020_Date eq '@{outputs('Compose')}'
But it cant conclude the flow:
It seems that the date and time are malfunctioning.
My imput date is dd/mm/yyy and the code is:
addDays(utcNow(),30,'dd/mm/yyyy')
It made the first error (on the previous post).
I exchanged it to the amrrican format: addDays(utcNow(),30,'mm/dd/yyyy') now it shows this result on imput/output as well the same error.
Please see my screen shot below.
In my example, Flow is referring to the column as ExpiryDate - if your output says Expiry_x0020_Date then use that.
Please note my date formatting: yyyy-MM-dd
Also, I did not use a compose action - there is no real reson to do so.
Sucess!
Hello All! Just a new issue: I have set up this reminder flow as a champ on another list (Task list, with due date reminder), BUT this one has a particular situation that when user set that a task is completed, they should stop receive the notification for that task.
How can I do this?
It would be best if you posted this as a new topic. That way it will easier for others to find, tag, etc..
Oh... I was thinking on it, but since too many don´t search and don´t read forum rules, I thought that this might be a continue of this issue...
Will create a new one! Hope you can support me there!
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
66 | |
58 | |
29 | |
27 | |
25 |