thankyou, but the flow is quiet different feom mine and im unable to create the screen action flow 

can u plz show me the flow to achieve occupancy rate for next seven days

I assume you want the chart to show occupancy for each of the next 7 days, meaning you'll need 7 data points, one per day. To achieve this, you can use a traditional loop with an If to calculate the value for each day.

If you can share your OML, I’ll be able to give you a concrete example based on your actual data.

here are the files 

here are the files 

Alright, as mentioned earlier, you can use a traditional loop starting from index 0. Use an If to calculate values for each of the next 7 days. Use your existing aggregate in a Data Action and filter it for each specific day. For every iteration, filter the bookings for that day and append the result to a list, which you'll then use as the chart's data source. 

Result:

Hi, thanks for pointing out the issue. I'm not sure what the expected range is, whether it's the next 7 days starting today, or from today through the end of next week (which would be 8 days). It might make more sense to treat this as a weekly chart.

For occupancy, if bookings aren’t the right metric, I believe it should be the total number of guests (adults + kids).

I’ve updated the OML so it now uses the number of guests. As for the other filter, it’s from the original OML and no further details were provided.

@udvisha kosti It would be helpful if you could clarify the actual requirement behind this. 

yes, number of guests is also interesting, i think, as a user, I would like insight in number of guests (for staffing of the bar) number of rooms booked (for staffing of room services) number of children (for staffing of child activities).

But that's not the point I was trying to make, the logic is only going to be correct if everybody only stays 1 night, because your filter only looks at the checkin date being equal to a given date, but if someone is booked for the first 3 days of next week, it should count on all 3 as occupancy, not only on the first day. 

The chart now only gives an idea how much front desk staffing is needed to do the checkins

to show what i mean :

(I am making the assumption that bookings don't contribute to occupancy on the checkout date)

filter in aggregate should be something like

and filter in ListFilter within loop should be something like

Also, the ListAppendAll doesn't make any sense to me, it should be a ListAppend.

And just as a spielerei, I also explored an option where we have a 'calendar' entity, so we can solve the entire thing inside a single group by aggregate, without having to apply filters in a loop afterwards.

See my attached changed OML, actions Get7DaysOccupancy and Get7DaysOccupancyInSingleAggregate.

Dorine