Solved: Auto-archive flow failing

ClaudiaMulder · ‎06-18-2019

Hi all, I have a problem with a auto-archive flow. I am at a loss here, so your help and insight is much appreciated.

What I want to achieve: on our intranet (SP Online) we use site pages to create news items. The Site Pages library is now filling up, and I want to auto archive items that are older than 30 days. Those items should move to another library: News Archive.

I found this flow somewhere and copied and edited it, but I can't figure out why it fails.

Maybe there's an easier way to do this? Let me know 🙂

thanks, Claudia

yashag2255 · ‎06-18-2019

Hi @ClaudiaMulder

@ClaudiaMulder wrote:

Something's not right with the Filter Query, maybe a language thing? Since the original flow was in English, and we use Dutch SharePoint. 'Modified it' = 'Gewijzigd' in Dutch. But I have changed that but the test generates the same error.

Can you try this in the filter query: Just add an 'eq' between the column name (Modified) and the variable. and enclose the variable in single quotes.

Gewijzigd eq '(var)'

Hope this Helps!

View solution in original post

yashag2255 · ‎06-18-2019

Hi @ClaudiaMulder

Can you please share a screenshot of the error message? That way we might be able to assist you better.

We can use the ODATA filtering to identify records older than 30 days. But let us first see the error message to identify the action where the issue is coming up.

Hope this Helps!

ClaudiaMulder · ‎06-18-2019

Hi, sure, here's the error message:

When I expand the Get Files properties, it says:

{
"status": 400,
"message": "The expression Modified it \" 2019-05-20T00:00:00.0000000Z\" is not valid.\r\nclientRequestId: 658881f3-7dd3-47e2-8c62-326f744ce225\r\nserviceRequestId: 658881f3-7dd3-47e2-8c62-326f744ce225"
}

thanks,

Claudia

yashag2255 · ‎06-18-2019

Hi @ClaudiaMulder

I can just see the error appearing on the action but not the error message. Can you please click on that item and see the error meesage and post a screenshot of that?

ClaudiaMulder · ‎06-18-2019

ah sorry , i was too late adding it to my reply. Here's what it says:

{
"status": 400,
"message": "The expression Modified it \" 2019-05-20T00:00:00.0000000Z\" is not valid.\r\nclientRequestId: 658881f3-7dd3-47e2-8c62-326f744ce225\r\nserviceRequestId: 658881f3-7dd3-47e2-8c62-326f744ce225"
}

Screenshot:

ClaudiaMulder · ‎06-18-2019

The string for the expression variable '30 dagen' is :

StartOfDay(addDays(utcNow(),-29))

Maybe something with timezones (utc) ?

ClaudiaMulder · ‎06-18-2019

Something's not right with the Filter Query, maybe a language thing? Since the original flow was in English, and we use Dutch SharePoint. 'Modified it' = 'Gewijzigd' in Dutch. But I have changed that but the test generates the same error.

yashag2255 · ‎06-18-2019

Hi @ClaudiaMulder

@ClaudiaMulder wrote:

Something's not right with the Filter Query, maybe a language thing? Since the original flow was in English, and we use Dutch SharePoint. 'Modified it' = 'Gewijzigd' in Dutch. But I have changed that but the test generates the same error.

Can you try this in the filter query: Just add an 'eq' between the column name (Modified) and the variable. and enclose the variable in single quotes.

Gewijzigd eq '(var)'

Hope this Helps!

ClaudiaMulder · ‎06-18-2019

Hi, thanks for your input!

At first I changed it to: Gewijzigd eq 'var' but that generated a new error: "Column Gewijzigd does not exist". That was strange because it does exist :). I changed column name to Gemaakt (= 'Created' in Dutch). No avail.

THEN I changed the column name to Created. And now the flow runs successfully.

So... apparently, column names must be in English. Now there's a lesson learned!!

Thank you for helping out!!

yashag2255 · ‎06-18-2019

HI @ClaudiaMulder

Glad that it worked. Just one more point, in the ODATA query, if you want to fetch records older than the time string, the operator should be "ge" (greater than or equal to) insted of eq (equal to)

Hope this Helps!

ClaudiaMulder · ‎07-16-2019

Hi, sorry to bother you again, but there's still something not right. After I had applied your fix, I ran a succesful test. After that, I just scheduled the flow. But I got another error message. This time the error is in the step 'Apply to each'. This time, I don't have a clue what could be the problem 😞

Are you willing to help out again? Please find the screenshot and the error message below:

{
"error": {
"code": 400,
"source": "flow-apim-europe-001-francecentral-01.azure-apim.net",
"clientRequestId": "edf504a5-fb85-44fb-91e2-ebf3d30ae0a1",
"message": "The response is not in a JSON format.",
"innerError": "<!DOCTYPE html>\r\n<html>\r\n <head>\r\n <title>Runtime Error</title>\r\n <meta name=\"viewport\" content=\"width=device-width\" />\r\n <style>\r\n body {font-family:\"Verdana\";font-weight:normal;font-size: .7em;color:black;} \r\n p {font-family:\"Verdana\";font-weight:normal;color:black;margin-top: -5px}\r\n b {font-family:\"Verdana\";font-weight:bold;color:black;margin-top: -5px}\r\n H1 { font-family:\"Verdana\";font-weight:normal;font-size:18pt;color:red }\r\n H2 { font-family:\"Verdana\";font-weight:normal;font-size:14pt;color:maroon }\r\n pre {font-family:\"Consolas\",\"Lucida Console\",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}\r\n .marker {font-weight: bold; color: black;text-decoration: none;}\r\n .version {color: gray;}\r\n .error {margin-bottom: 10px;}\r\n .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }\r\n @media screen and (max-width: 639px) {\r\n pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; }\r\n }\r\n @media screen and (max-width: 479px) {\r\n pre { width: 280px; }\r\n }\r\n </style>\r\n </head>\r\n\r\n <body bgcolor=\"white\">\r\n\r\n <span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1>\r\n\r\n <h2> <i>Runtime Error</i> </h2></span>\r\n\r\n <font face=\"Arial, Helvetica, Geneva, SunSans-Regular, sans-serif \">\r\n\r\n <b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.\r\n <br><br>\r\n\r\n <b>Details:</b> To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<br><br>\r\n\r\n <table width=100% bgcolor=\"#ffffcc\">\r\n <tr>\r\n <td>\r\n <code><pre>\r\n\r\n\r\n\r\n<configuration>\r\n <system.web>\r\n <customErrors mode="Off"/>\r\n </system.web>\r\n</configuration></pre></code>\r\n\r\n </td>\r\n </tr>\r\n </table>\r\n\r\n <br>\r\n\r\n <b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.<br><br>\r\n\r\n <table width=100% bgcolor=\"#ffffcc\">\r\n <tr>\r\n <td>\r\n <code><pre>\r\n\r\n\r\n\r\n<configuration>\r\n <system.web>\r\n <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>\r\n </system.web>\r\n</configuration></pre></code>\r\n\r\n </td>\r\n </tr>\r\n </table>\r\n\r\n <br>\r\n\r\n </body>\r\n</html>\r\n"
}
}

yashag2255 · ‎07-16-2019

Hi @ClaudiaMulder

The error clearly is in the File Identifier of the Get file metadata action. Can you please check that you are using the right option from the dynamic selector for the file identifier?

Hope this Helps!

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!