Thank you i was able to get it working,
there was a couple of things i needed to change one was the 2nd condition, i had to set it too
But once again, i really wish to personally thank you. This has saved my job. If your ever in Australia send me a message.
@ScottShearer wrote:@Anonymous
While the timezone may impact the results, it will not cause an error. The timezone has no impact on the date format. Also, SharePoint stores everything as UTC time.
Can you verify that the terminate action is set to success? If not, set it to success and test again.
When you test again, experiment with entries that are 29 and 31 days forward and see if you get any results. Once you get results, I'll explain how to control for the timezone.
Hi Scott,
@ScottShearer wrote:@Anonymous
While the timezone may impact the results, it will not cause an error. The timezone has no impact on the date format. Also, SharePoint stores everything as UTC time.
Can you verify that the terminate action is set to success? If not, set it to success and test again.
When you test again, experiment with entries that are 29 and 31 days forward and see if you get any results. Once you get results, I'll explain how to control for the timezone.
I was able to get it too work however its looking at completed work orders (from the previous system) so what im going to do is delete all the old ones and create a another list called completed and after each task is marked as complete a flow sends it elsewhere,
However what happens if i have say one date column and another both during the same period? i guess ill have to make a yes/no column call it DATECHECK1 and get the odata query in the 2nd Get items to be DATECHECK1 eq 'Yes' and Asset eq 'Asset'
A million thanks i slept well last night,
what i will do is finish it and the when its perfect today, ill mark is as solved for your last response and i will put up a screenshot for anyone looking to do the same thing in the future.
@Anonymous
While the timezone may impact the results, it will not cause an error. The timezone has no impact on the date format. Also, SharePoint stores everything as UTC time.
Can you verify that the terminate action is set to success? If not, set it to success and test again.
When you test again, experiment with entries that are 29 and 31 days forward and see if you get any results. Once you get results, I'll explain how to control for the timezone.
@ScottShearer wrote:@Anonymous
Can you please post a screen shot of your Flow - at least the part where you have the OData filter.
Also worth nothing that im in Australia and the Site is set up to AEST +10 (Brisbane). Could it be the date format?
@ScottShearer wrote:@Anonymous
Can you please post a screen shot of your Flow - at least the part where you have the OData filter.
Certainly,
Also the code here is copied and pasted,
Compliance_x0020_Date eq '@{addDays(utcNow(),-30,'yyyy-MM-dd')}'
afaik it should be working as the '' are in the right spot. I feel cursed haha
Edit: Removed identifying info from the image
@Anonymous
Can you please post a screen shot of your Flow - at least the part where you have the OData filter.
@ScottShearer wrote:@Anonymous
Below is a Flow that should get you started.
I use a column called AssetRegisterID to link the work order items to the Asset register.
You can extend my solution by adding "or" statements to the Get Items action for the Asset Register list.
Here is a link o a post that better explains OData filters (used in the filter query).
Hi Scott,
I dont think the odata get date or add date is working, the value of the body is []
Ive also check to make sure there is one date that is due (i built a few test assets)
@ScottShearer wrote:@Anonymous
Below is a Flow that should get you started.
I use a column called AssetRegisterID to link the work order items to the Asset register.
You can extend my solution by adding "or" statements to the Get Items action for the Asset Register list.
Here is a link o a post that better explains OData filters (used in the filter query).
Thankyou so much for this, I wish i could better convey the emotion of grattitude, i have for you for this through text.
I should send you some beers, ill put it in and mark as solved when it works 🙂
@Anonymous
Below is a Flow that should get you started.
I use a column called AssetRegisterID to link the work order items to the Asset register.
You can extend my solution by adding "or" statements to the Get Items action for the Asset Register list.
Here is a link o a post that better explains OData filters (used in the filter query).
@ScottShearer wrote:@Anonymous
Can you tell me what should trigger your Flow? Should it run only when the Asset Register entry is updated? Should it run on a schdeule (daily?) looking and loop through all items in the Asset register list?
Hi Scott,
I guess id perfer a Schedule flow, that runs each morning id like it to check each of the four date of service columns and create a new item with a Asset ID (its the machinery number) and Whichever date column is expirered and if the sameflow runs the next day then not add a new item?
Does that make sense?
Cheers
Essentially what im doing is once the date is flagged and a new item is created, someone else will look at that work order list via powerapps and then they will mark a choice column as complete and then an email will be sent externally to say this task is done and here is the list item marked as complete and who performed it, and we can give them access to just that list (i can do this part of it, i thought i could do this part)
Michael E. Gernaey
497
Super User 2025 Season 1
David_MA
436
Super User 2025 Season 1
Riyaz_riz11
244
Super User 2025 Season 1