expiration notification

[3cdoug]

addDays(utcNow(),30,'MM/dd/yyyy')

I want to use this filter to give me 30 days prior to my expiration date? Any Pointers?

[TheRobRush]

if theres nothing in the 60 day range currently it is fine, i wrote the code to have each category only include items that are solely in its range, didnt really want a situation for you where something 30 days away showed up as 30, 60, and 90 days away

[3cdoug]

I'm  still getting schema validation failure, its just telling me that the ParseJSon are failing so IDK what to do. Thank you for your continued help though 🖖

[TheRobRush]

usually that means you copy pasted the first steps output wrong the first time around. BUT how are you getting 30 and 90 output if the parse json is failing? if its only failing for the 60, just copy that step 1 output again, and go back in find your 60 day parse, click create from example or whatever it says and then paste it in  again, (or maybe easier for you, copy the 30 day parse json to your clipboard, add new step (then click form my clipbaord and paste your 30 day in) then change the body reference to the 60Days

[3cdoug]

I mean in the first steps where you say pause and run the flow, I get a 30 and 90 day output in the schema but nothing in the 60. I've tried using both the 30 and 90 day outputs but I still get the ParseJSON error and the flow fails

[TheRobRush]

 me what you have here

and include the name of the original date column in the splist (not the calculated one) along with a screenshot of the error in full

[3cdoug]

[TheRobRush]

Lets try this, just to keep it simple for a single test.

Create a new flow, make it just a manual run one via button click for now, we can chaneg the trigger later.

Then set your site address, list name, and filter query on a get items

Now add a new step, and make it a filter array, that does this

from

outputs('Get_items')?['body/value']

or just pick value from the dynamic options

and then

@lessOrEquals(item()?['DateCompleted'], addDays(utcNow(), -330))

NOW AT THIS POINT WE STOP, SAVE, AND CLICK TEST, Then run a  manual test

go to the filter array and copy everything here, dont try to click show raw or open it in any way just triple click in the area below and it should highlight it all, ctrl c, then click edit in top right

Now that we are back in edit mode, click add new step and make it the parse json

in content add the body of the 30days you made, should b e in dynamic choices, if not

body('30Days')

is the reference

Now click generate from sample

paste in everythign we copied from the output

then click done

Now stop, save, and run it again and see if you are still getting a parse error

[3cdoug]

Yes, I still receive the Parson_JSON failure.

And Again, thank you for your help and assistance in this

[TheRobRush]

managed ot make it fail, then checked what the new schema was vs tge old working, and came up with this idea. check schema and see if you have something liek this happening

you will see in the good version first item in propertie sis @@odata, but in the failing version (also acquired via copy and paste weirdly) I get ItemInternalID (which is a few lines down in the good version) you might check this and if yours looks more liek the right hand side manually edit top of your schema to be like

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "@@odata.etag": {
                "type": "string"
            },
            "ItemInternalId": {
                "type": "string"
            },

 the above is everything up until "ID":

[3cdoug]

So I've done that, but I still get an error.

I get this: