Using the end point
GET /workspaces/{workspaceId}/user/{userId}/time-entries
I'm only able to retrieve time entries for a user going back about 14 days.
Am I able to retrieve older entries through the API?
I have tried the API using no start time, and using a start time 30 days ago and there are no results older than 2019-08-16T19:00:00Z (today is 2019-08-28)
I also tried emailing support#clockify.me and they told me to create an issue here.
I expected to be able to retrieve more than the last two weeks worth of entries.
Jovana from Clockify Support got back to me and the issue was default page size was too small. I added the parameter pageSize=10000 to allow me to retrieve more than a few days worth of entries.
Example
https://api.clockify.me/api/v1/workspaces/{0}/user/{1}/time-entries?page-size=10000
I am in the process to add FullCalendar v4 to our react application and I'm pretty new to FullCalendar, so excuse me if I ask a basic question.
I searched both the documentation and StackOverflow, but couldn't find any hints to my current problem. Let me briefly describe our goal scenario:
We want to load and render the events for a whole year and show a date range of about 40 days (a whole month and additionally 5 days from the last and the next month) to the user. The user should be able to scroll through the whole year with the scrollbar.
The first question is whether FC4 already provides the functionality with which we can achieve our goal. I tried to define a custom view of type 'resourceTimeline' with a duration of 30 days and additionally set the 'validRange' to the current year. This gives me the look I want, but unfortunately it is static - the scrollbar is not visible as long as the screen can display the whole area of 40 days. With the next/previous buttons I can switch between the 40 days segments, but I'd rather use these buttons to switch between years and use the scrollbar to scroll within the year.
We have now tried to set the 'visibleRange' to the current year and programmatically scroll to the current date in the 'datesRender' function. The problem is that we can't decide whether FC4 was initially loaded (where we would scroll to the current date) or whether a user scrolled manually to another date in the timeline and edited an event there. In this case the scroll position should be kept.
So what we are missing is the matching callback that tells us that the 'executeRender' function has been completely executed. The question at this point is how and where I can provide an application specific callback function that is triggered after all dates and events have been rendered. I also saw several internal success callbacks. Is it possible to overwrite them?
Any ideas and hints are highly appreciated.
Thank you very much for thinking along.
To get some "visual alerting", I'd like to draw simultaneously two curves on the same graph in Grafana:
current time-window graph
same graph but with 7 days ago data
The idea is to be able to compare data evolution on the same day in the previous week.
I could not find a Graphite function for that (but I may have missed something in the doc).
Is there a way to do it?
You can use timeShift to make a metric in grafana with your series shifted back a week.
This kind of thing is also a good application for series-specific display overrides in grafana, so you can make the shifted series display differently from the current data.
I need a global interval template for recurring events.
I am constructing a schedule management web app. I have a set of event happening periodically up certain moment in time. For example I a have a train schedules. They repeat them selves every week for certain winter or summer periods. Using Date module I would have to enter ending and beginning dates of let say summer period for each train route.
What I want to do is to simply add a taxonomy term which would hold repetition interval with some holiday exclusions...
This more Drupal philosophy question yet I think that others had ran into similar issues before.
Maybe I am looking to this problem from a wrong angel could somebody could lend me fresh set of eyes.
I have a database that tracks employee’s data for the current year and previous years.
In examples below I will use calendar years (years start in Jan and end in Dec)- this is not always the case, some users have their year running from July to June- or April to March, etc.
There are many tables that, with a few heavy calculations, make a view of the employee’s data at this point in time.
This current year’s data is what users look at mostly. But data from previous years impact on this year (so, a change made to the 2008 data- will have a knock on effect on 2009, and then into 2010 and so onto this year).
Obviously, this has a negative impact on performance when viewing reports as viewing this year’s data will mean trudging through all the previous years- calculating and creating views until the end result is found. As the application ages, this problem will get worse and worse- say in 2015, anybody using the system from its inception (2008) will be waiting for a long time to get their data.
We plan to freeze previous years data so instead of having data from 2008, 2009, 2010 and this year’s data- we would have one block with the previous year’s data (with all calculations done for those previous years) and this year’s data.
In this way, we would have the end results data for all the previous year’s already calculated and we would only need to add to this year to get the final result.
Obviously, we would have to prevent users from entering/updating data in previous years.
My question is what is the best way to achieve this? I presume you would need some process that waits until the new year and does some calculations.
Thanks in advance,
ViperMAN.
the approach you describe is normally referred as data archiving, you can have some queries a DBA runs manually every year the first working day after the new year party so the calculated data is prepared and stored.
Also, your application needs to deny users to modify previous years data, if I have got it right.
One approach I was thinking works as follows:
Create a table that holds the result of the previous years calculations.
Prevent all addtions/deletions/updates to previous years from the app tier.
Change reporting so that queries would consult this table instead of trudging along, calculating everything out each time.
Have a daily process that would:
Check if today was the first day of an employees year-
If yes, get all of the elapsed year's data and add them to all the previous years.
Obviously, this is a simlified version- but one that I think could work.
Thoughts?
If you have data that should not be edited, and you can define what that data is, then I would use a combination of stored procedures and security settings to ensure the old data stays accurate.
If you used stored procedures as a filter, you can have logic in your stored procedure that checks the record against the current DateTime and only allows the update if everything fits your requirements.