Improve oData request
Make available Timephased data on a Monthly basys additionally to the time by DAY.
Request oData feed on a daily basys is not usable on "big" projects of some years. Be able to request on a monthly basis will decrease the amount of data to request and store.
You can now rollup timephased data by day, week, monthly or by fiscal period for:
Regarding the number of performance issues we have with Timephased odata feeds, I think it could be a very good idea to get timephased by day, or by month or by quarter. Most of customers don't need to get data by day when they build their monthly, quarterly of annual reports.
But have the choice of the timeframe aggregation is a very improvement, in term of volume of data and performance.
Where would By Day be used if we provided by month?
Denis Grangé commented
Essential to be able to pool Timephased Data!
Fabien EVRARD commented
This would be really helpful for Project Online requests indeed, since the interesting reporting part is focused on timephased data (assignments in particular)