No, absolutely, I just wasn't aware that you needed the logic to get the years all set up, too. I was giving you the barebones to ensure that the actual query worked.
All you need to do is present the ODATA filter with the dates that you wish to be greater than or equal to in the first instance, and less than in the second. In the date format that your systems are setup for.
So either use an expression to generate the dates in the ODATA field, or have a variable/compose show them.
This works for the greater than or equals expression which you can either place in the field, or work it out as a string value in a Variable or a Compose:
concat(utcNow('yyyy'),'-01-01')
Here's the less than:
concat(add(int(utcNow('yyyy')), 1), '-01-01')
Here's how I've used it in my example flow where my date field (which also has time values in the actual list) is called "dateOfDeparture":
