cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
long Advocate I
Advocate I

Time Trigger

Trying to set a trigger for a time off request based on how many hours from the created date and time until the date and time of the day off.  We have a different approval process for time off requests made with less than 72 hours notice until the day off.  In share point I have made a calculated collumn which takes the date/time of the day off request and subtracts the date/time created "=INT(([Date & Tour Start Time of Day Off ]-Created)*24)" this gives me a number of hours until the day off.  I also have a collumn in sharepoint that is set to 72, for 72 hours. 

In flow Im using a sharepoint list new item created trigger. This flows to a condition "@less(outputs('Compose_2'), outputs('Compose_4'))".  I used compose to format both values into integers, resulting in Compose2 (this is the calculated time collumn) and Compose4 (this is the 72 collumn). 

The flow runs but the logic in the condition does not return results as expected.  It will say that 78.000000000 is less than 72 which incorrect, so It will not follow the correct flow.  I am wondering if the zeros after the decimal point is affecting the results?  Any assistance will be appreciated.  

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support
Community Support

Re: Time Trigger

Hi @long,

 

I am afraid I don't fully understand what your issue is.

Could you share the details of your Flow configuration?

The "78.000000000 is less than 72. incorrect" that you mentioned refers to an error in the operation or a false display in Condition?

If the result is false, it is logically correct. If it is an execution error, please provide error message.

You could consider using the float() function to turn both values into a float type.

Please provide more details and we would provide proper workaround for you.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
Community Support
Community Support

Re: Time Trigger

Hi @long,

 

I am afraid I don't fully understand what your issue is.

Could you share the details of your Flow configuration?

The "78.000000000 is less than 72. incorrect" that you mentioned refers to an error in the operation or a false display in Condition?

If the result is false, it is logically correct. If it is an execution error, please provide error message.

You could consider using the float() function to turn both values into a float type.

Please provide more details and we would provide proper workaround for you.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

long Advocate I
Advocate I

Re: Time Trigger

Used the float() function on the two inputs and it solved the problem.  Thanks!

Helpful resources

Announcements
firstImage

New Ranks and Rank Icons released on April 21!

The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Automate Community!

firstImage

Now Live: Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Community Summit North America

The top training and networking event across the globe for Microsoft Business Applications

Top Solution Authors
Users online (7,832)