Unanswered

ODATA and filtering using runtime variables

(0) Share

Report

Posted on by MThomas

I'm building a flow that connects to a Sharepoint Online list and filters the list down using ODATA. I can get the basic filters to work, but I need one final filter that uses the current system datetime to compare to a datetime value field in the list. For example:

Disposition eq 'Initial' and Status eq 'Pending' and SchedConfDate le =Now()

Where SchedConfDate is a datetime column from my SPO list. I need to filter my data down to just those list items whose SchedConfDate is less than or equal to "Now" or "Sysdate" or some other runtime variable/parameter that reprents the current date and time. Does anyone know if ODATA supports using these runtime variables because I have not been able to get any permutation of "Now" or "UTCNow" to work. Or is there another way this could be achieved?

Best Regards,

Mike

Categories:

Building flows

I have the same question (0)

All responses (8)

Answers (0)

v-monli-msft on at

Like (0)

Report

Hi @MThomas,

I have escalated this issue to the pg and will update here if I got further information.

Regards,

Mona

Was this reply helpful? Yes No
efialtes 350 on at

Like (0)

Report

@MThomas
Have you tried building the ODATA expression in a Compose action block? Soon we will be able to invoke WDL functions in acton blocks' input fields as announced in https://flow.microsoft.com/en-us/blog/use-expressions-in-actions/ ; but I guess the rollout of such feature has not been completed yet, so Compose action block is a good workaround. The expression in the screenshot is quite simple, but you can buid more complex expressions by using WDL expressions like utcnow()

Was this reply helpful? Yes No
MThomas 11 on at

Like (0)

Report

This sounds like EXACTLY what I need, but I too do not see Expression as an option right now. When will this be rolled out to everyone?

Thanks,
Mike

Was this reply helpful? Yes No
efialtes 350 on at

Like (0)

Report

@MThomas
It seems the rollout has been completed, I can see the expressions tab!

Was this reply helpful? Yes No
MThomas 11 on at

Like (0)

Report

I'm still struggling with the syntax. When I try to write the filter in basic mode:

It fails saying that "greater" is not recognized. I figured this is because I was mixing basic and advanced syntax, so I tried it all in advanced syntax:

Where it fails saying that "and" is not supported or it is invalid. So, I think I have syntax errors. Any idea on the correct syntax for:

Disposition = "Initial"
Status = "Pending"
SchedConfDate > utcnow()

???

Any help is greatly appreciated!

Thanks
Mike

Was this reply helpful? Yes No
efialtes 350 on at

Like (0)

Report

@MThomas Maybe the problem is because of mixing WDL sintax+expressions with ODATA sintax+expressions. I would be great if Flow team can confirm if the following link is an official and thus valid ODATA tutorial link for Flow related ODATA expressions:
https://msdn.microsoft.com/es-es/library/hh169248(v=nav.90).aspx

What I see is that 'greater' a WDL expression, 'gt' seems to be its equivalent in ODATA. Please note utcnow() is also WDL, so before injecting it as part as an ODATA expression, you must make sure it has been already interpreted into the proper value.

After executing the flow, you can verify both inputs and outputs of each action block, thus you can see if the ODATA expression has been built according to your expectations

Was this reply helpful? Yes No
ReflexBCS 7 on at

Like (1)

Report

In case other people are still looking - the following approach worked for me;
1) add a "compose" action to construct the filter; Inputs = Title eq '<<insert variable from previous step>>'
I just typed the column name without anything around it,
then type: eq
then (single quote to open) type : '
then clicked into dynamic content to select the value from previous step (when item is created or modified)
then (single quote to close) type: '

2) Next create the "get items" step
Select your site and list
Go to "Advanced Options" to show the Filter Query
Click and select from dynamic content "Output" from the Compose step.

You're done. Hope this is helpful.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (2)

Report

You didn't really have to add that "Compose" step. Just use the same syntax in the Filter Query field of the Get items. Worked for me:

Was this reply helpful? Yes No