29. May 2016
With great pleasure Dataloy presents API 3.0
Issues resolved - listed by user story
| Section |
|---|
| Column |
|---|
| | Excerpt |
|---|
Highlights of this Release:
|
|
|
Highlights of Dataloy API 3.0
| Section |
|---|
| Column |
|---|
| 
|
| Column |
|---|
Update Sub-Objects and Lists and Update in a Single Transaction |
|
...
PUT has been improved to a more standard way of handling arrays. For more information, see the API Knowledge Base > update array section.
| Note |
|---|
This is an API change. Customers who include arrays in PUT requests need to make changes. Behavior prior to Dataloy API 3.0: - Including an array in PUT always inserts the elements in the array.
Behavior from Dataloy API 3.0: - Array elements without a key will be inserted.
- Array elements that includes a key will be updated.
- Array elements excluded from the array will be removed from the array.
For examples, see API Knowledge Base > update array section. |
| Section |
|---|
| Column |
|---|
| 
|
| Column |
|---|
As PO I want to have the Cargo business logic as is in Kara implemented in DLP correcly |
|
As PO I want to have the Cargo business logic as is in Kara implemented in DLP correcly
...
| Section |
|---|
| Column |
|---|
|  Image Removed
|
| Column |
|---|
As API user, I want to data changed outside API do be refreshed, so that I can trust data received by the API |
|
As API user, I want to data changed outside API do be refreshed, so that I can trust data received by the API
...
PUT Subobjects in a Single Transaction |
|
API 3.0 introduces the ability to update subobjects in a single transaction. Previously an update of the main object and a subobject had to be separated in two PUT requests,resulting in two transactions. This new improvement is backward compatible. More information and examples: see API Knowledge Base > sub-object section.
Related Content
| Expand |
|---|
| title | Expand to see related content |
|---|
|
| Wiki Markup |
|---|
{dynamiccontentbylabel:showLabels=false|showSpace=false} |
|