Start date and End date do not populate correctly when pm_project_task record is created from script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-02-2024 07:49 AM
I have been asked to create a Record Producer so that managers can create Project Tasks directly from the Service Catalog. They just need to fill Project, Short Description, Assigned to, Planned Start Date, Planned End Date and Planned Effort fields using the form. This data is introduced using a MRVS, and then a script takes the values from this variable set and creates a record for each row.
Project, Short Description and Assigned to are correctly filled in the pm_project_task record, but Planned Start Date, Planned End Date and Planned Effort are not being updated as they should. In order to solve this problem, I have tried to create a pm_project_task record directly from background script and something very strange happens: as you can see in the images attached, I set the value of end_date to '2024-12-11 14:49:57', after the update it says the value is still that, but if we check the created record it appears to be another different date I did not choose.
However, if I create the pm_project_task record directly from the form, then start_date is correctly filled.
Can anybody explain me what is happening? I have no more ideas of how to solve it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-02-2024 09:18 AM
The end date could be calculated when using the script based on Business Rules running on the pm_project_task table. When you create a task via the form you are populating more data than just the end_date. I would instead focus on the flow or script that is creating the tasks to determine why the three fields are not populating/correct from the MRVS.