Using API - Unable to save date value?
We have upgraded a project from 3.7 to 4.0. Now, values in custom date fields are not displaying.
Additionally, when trying to save a custom date value through the API (.NET), the values are not saving.
Any ideas?
mmatos
· 1 |
|
Thursday, June 30, 2011, 3:40:49 AM |
0
|
Did you get the upgrade screen when logging in to Gemini as Administrator? If so, did it run without any warnings? |
||||
|
0
|
Good Morning! I did not perform the upgrade myself, so I cannot speak to that. Is there a way to perform the change after the fact? |
||||
|
0
|
Yes, navigate to: http://your gemini url/admin/upgrade/upgrade.aspx |
||||
|
0
|
Thanks Mark. I will look in to that. What about when trying to save a date value using the API? We are still using the 3.7 libraries. Do we need to change in order to be able to save dates into custom fields? |
||||
|
0
|
Yes, we have made changes to the custom field data entity. Now it has a field for each type. |
||||
|
0
|
Hello, We are still struggling to get this to work. We are setting the DateData field, but the value is not being saved in to the database. Can you please post a working .NET snipping of creating an issue and populating a custom date field with a date value? Thank you. |
||||
|
0
|
There you go, this assumes issue id 527 exists and the custom field at the 8th index is the date one:
|
||||
|
0
|
Can I assume from this that the old method of assigning the custom data fields to the issue object (issue.CustomFieldData = [an array of CustomFieldDataEN]) no longer works? |
||||
|
0
|
Also, is it possible to save multiple with one call? In the past we would create an array of CustomFieldDataEN and assign it to the issue, thereby saving several custom data fields simultaneously. Some of our projects have up to 10 custom data fields and making a call for each one seems wasteful. |
||||
|
0
|
It will work on issue creation. Share your current code as nothing as changed in that respect. |
||||
|