Behavior of create task API call?
I'm having some issues with the API task create method - some could probably be cleared up by documentation, but some I think are bugs.
1) If I create the task specifying both start/end date and duration, it appears that start/end date takes precedence and the duration specified is ignored.
2) It appears that the duration_type value is being ignored and that the duration is always in days. I.e., I specify "duration=20" and "duration_type=hrs", the duration for the task is set to "20 days" (with the work matching).
3) It also appears that there is no way to set the work without setting either duration or start/end times - there are tasks we would like to create where we know the task will be done "part-time" over a calendar period, so the work isn't purely based on the calendar duration of the task.
1) If I create the task specifying both start/end date and duration, it appears that start/end date takes precedence and the duration specified is ignored.
2) It appears that the duration_type value is being ignored and that the duration is always in days. I.e., I specify "duration=20" and "duration_type=hrs", the duration for the task is set to "20 days" (with the work matching).
3) It also appears that there is no way to set the work without setting either duration or start/end times - there are tasks we would like to create where we know the task will be done "part-time" over a calendar period, so the work isn't purely based on the calendar duration of the task.
Topic Participants
billt
Sathyanarayanan SG
Sticky Posts
Building extensions #10: Fetch customized user inputs, store them globally at the app level, and access them across entities
This data storage concept enables you to store data related to your extension for both entity properties and extension properties. In our previous piece, we looked at how to store data for entities using entity properties. In this post, we'll look atBuilding extensions #9: Store, retrieve, and access entity-specific data in widgets using data storage
Data storage - Overview Storing data related to the extension you are working on is essential. It can be saved as key-value pairs for an entity or extension, known as entity and extension properties, respectively. Data can be saved for the following entitiesBuilding extensions #7: Create custom widgets for a simplified end-user experience
Discover the benefits of using widgets! We explored the significance of widgets, prerequisites, and the availability of JS SDK methods as part of our previous post. In this post, let's go over a detailed example of using widgets along with certain ZohoBuilding extensions #6: Custom user interfaces with Widgets
Welcome to our post on Widgets for Zoho Projects! In our last post, we explored the significance of the connections feature, showed how to use it, and provided an example use case. In this article, we'll look at the importance of widgets, another featureBuilding extensions #5: Integrating applications with Zoho Projects through Connections
In our last post, we discussed the essential features that a Zoho Projects extension can provide. Starting with this post andin every subsequent post going forward, we'll go through each of those features in depth, one by one, with an example use case.