I'm trying to use patch as an update option for a google tasks from the API https://developers.google.com/tasks/reference/rest/v1/tasks/patch. So far as I understand it should update only sent fields, but even if I'm sending only title, it overrides time portion, meaning: I add google task from google tasks app, set date and time; then in my app with https://developers.google.com/tasks/reference/rest/v1/tasks/patch I'm sending title update, task becomes all day and losing time portion
What I'm doing wrong ?
This is an issue that has been reported
The issue is tracked on Google's public issue tracker here: https://issuetracker.google.com/issues/128979662
The Support documentation says you can report this on Google Issue Tracker. In this case I would find the report created for this and upvote it.
As you mentioned Google Tasks documentation says that the field due should not be affected if your are not explicitly changing that field:
Due date of the task (as a RFC 3339 timestamp). Optional. The due date only records date information; the time portion of the timestamp is discarded when setting the due date. It isn't possible to read or write the time that a task is due via the API.
Related
I am facing issue with auto-scheduling when i am using task level calendars with different working days and holidays along with link lag property to set lag and lead time between tasks. I am using forward planning with type 3 links between dependencies.
Then the start date of some tasks in not following the lag time passed in the links.
Note: I am not using time constraints still the task start and end dates are not correct after auto-scheduling.
But if I remove the task level calendars then the auto scheduling is working fine with lead and lag time between tasks.
According to your description, it is similar to a known bug in DHTMLX Gantt, but maybe it happens because of something else.
To be sure that it is a bug, please reproduce the issue in the following snippet, then click on the “Share” button and send me the link:
http://snippet.dhtmlx.com/5/3fae1b026
Or send me a ready demo with all the necessary files so that I can reproduce the issue locally.
I run into a problem parsing RSS feeds with spring-integration-feed. I followed the example at
https://spring.io/guides/gs/integration/
My feeds do not include a published date. According to the RSS specifications, the dates are not required.
As the pubDate is null, the entry is not added to the queue of SyndEntry. See FeedEntryMessageSource.java
Is there a workaround for this?
The FeedEntryMessageSource uses that to detect new entries, without it, you'd get all the entries on every poll.
The only work-around would be a custom message source - you can invoke it from an inbound channel adapter.
If you have a proposal for another mechanism to detect new posts, feel free to open an improvement JIRA Issue.
I would like to ask you for help with google admin sdk, User Usage Reports. I got following questions:
One of the parameters used to retrieve a usage reports is a date. Unfortunately for current date the reports are not yet available - I must use a date few days in the past. Is there any official rule, recommendation or any advice how to know most recent date for which the reports are already available? Should I query reports for a one day in the past, 3 days, week or...? I just want to have the latest results without worrying about the date...
Even more: sometimes the returned reports are OK for one of the google apps but for other one - like docs - I got warning that its not ready. So my question is: how to get most recent data for all of the apps? (mainly: accounts, docs, gmail).
I am using "all" parameter to retrieve all accounts at once.
Second question is related to first one: assuming I receive partial data - for example no reports for docs - is it possible that when I retrieve reports for all accounts (emails) some of them will have reports ready and some of the only partial data? Or the reports are always either ready or partial and for all accounts (emails) I should expect the same, full or partial data?
Thanks in advance!
Is there any official rule, recommendation or any advice how to know most recent date for which the reports are already available? Should I query reports for a one day in the past, 3 days, week or...? I just want to have the latest results without worrying about the date...
UserUsageReport returns Google Apps service activities across your account's users. the get() method retrieves a report for a set of account users. You can query for any date value provided that its timestamp is represented as ISO 8601 and should use your account's timezone.
how to get most recent data for all of the apps? (mainly: accounts, docs, gmail).
I'm guessing you're using CustomerUsageReport, it may take a while to process a report and thus you may have to retry to call it again after a few hours.
Second question is related to first one: assuming I receive partial data - for example no reports for docs - is it possible that when I retrieve reports for all accounts (emails) some of them will have reports ready and some of the only partial data? Or the reports are always either ready or partial and for all accounts (emails) I should expect the same, full or partial data?
I think this will depend on if the data are now available or not. You can test out various parameter values when accessing the API to test it out.
I have been caching Google calendar event data locally in a local database using the python api for v3.
I have this ID cached locally 16...hk_20140530T010000Z. The event has been deleted by a user using Google Calendar on the web, and was not deleted by any scripting. The user reported the event was still appearing in her reports from our local cache.
I investigated, assuming there had been a problem at some point in time and the scripts had simply missed canceling this event (I use updatedMin so I thought maybe something could have theoretically been missed.) However, even when I ran a full query of all data for this calendar this instance of the recurrence was nowhere to be seen. There were plenty of others in the recurrence that appeared, but this instance did not exist in the results from Google, cancelled or otherwise.
I pull these IDs directly from the results from google when I save them in the database, and the fact it exists tells me it had to have existed at some point. The fact it is no longer listed has me puzzled, as it should be there with a status of canceled from my understanding.
Does anyone have any suggestion on why this may be the case? We have 200+ calendars I sync and deleting and re-importing on a regular basis would be a very time consuming process.
Thanks.
Event deletions can disappear after a while. Make sure to correctly handle the 410 response code when using old sync tokens / modified since values (http://developers.google.com/google-apps/calendar/v3/sync).
I am working on mailchimp integration.
I need to pull campaign stats (opens and clicks) and put it in my local database.
Using mailchimp api i am getting the list of all the users with their action taken.
But my issue is how to keep data sync at all time.
Is there any way to skip that data from mailchimp api that i had synced already.
The problem is the entire data set can change between calls and there is no 'since' parameter... The only way to get an updated picture is to query all records and update....
Keeping stat "data synced at all times" really would just depend on your solution (have it query for updates when you/your users access that section...)
You could expidite the update process by keeping track of previous calls/updates with the timestamp (keep track of the timestamp and only update/add records that are newer than the last sync... )
As I said, there is currently no "since" command for the campaignEmailStatsAIMAll method (and no direct equivelent in the export API...)
A 'since' parameter would actually be a good feature... So if coding your own solution to track updates via the timestamp is undesirable, you may want to ask the question in the google group or post a feature request in the google code project:
http://code.google.com/p/mailchimp-api/
EDIT: I just opened the feature request as it may solve a similar issue for an upcomming project:
http://code.google.com/p/mailchimp-api/issues/detail?id=60