Update API Call Issue in WCO.

@Irfan.Khan
I would like to know know one more question regarding update request of WCO API.
previously i have observed that when i run postman application using put request with the individual/Organisation data, it would update the data what we sent irrespective of remaining fileds like secondary/custom (the data would remain as usual). but later on i came to notice that when I use the same PUT request i saw only the fields that were send was updated and remaining secondary/custom fields remains Null(empty). this was so surprising for me.kindly help me whether the API calls of WCO has been changed Recently?? so as to change the code accordingly.
Best Answer
-
Hi,
Can you tell me exactly when is previously?
Also, to explain you the update case API -
Suppose below is your existing case details with secondary fields as shown-
Scenario 1:
Name: Donald Trump
secondaryFields[
{ "typeId": "SFCT_1", "value": "MALE", "dateTimeValue": null },
{ "typeId": "SFCT_2", "value": null, "dateTimeValue": "1961-12" },
{ "typeId": "SFCT_3", "value": "USA", "dateTimeValue": null },
{ "typeId": "SFCT_4", "value": "IND", "dateTimeValue": null },
{ "typeId": "SFCT_5", "value": "ABW", "dateTimeValue": null}
]
Scenario 2: Now If i want to update the case by only changing the name to Vladimir Putin and I don't pass the above secondary fields in the update case request payload, the secondary fields will be lost and will be updated to blank.
Name: Vladimir Putin
secondaryFields[]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Basically, the update case updates the case with the data or fields that you're passing in the request if you wish to keep Secondary fields of a case as same and would want only certain data to be changed you must include the secondary fields/custom fields in your request payload and not pass it empty, if you pass it empty it will be overwritten to blank!
Hope this answers your query.
Feel free to reach out if you need further explanation on this!
Thanks,
Mehran Khan
API Technical Consultant
0
Answers
-
@Mehran.Ahmed Khan
The word previously terms 3-4 weeks ago.so if in this case, i need to pass the entire fields data even though i need to update a single name field. i think that would burdens the payload data and probably leads to poor performance.
the above mentioned Scenario 2 will misleads the case i think. since on update API calls we need to update the necessary fields and the remaining should be same. Hope you got my point.
thanks in advance.0 -
I totally understand your point, but when you pass secondary fields as empty while updating the desired fields, the API would think that you're updating the secondary fields to empty as well, and I don't believe it would cause any performance issue as our APIs are designed to handle payloads with/without secondary or custom fields in them.
Regards,
Mehran Khan
0 -
Just wanted to check with you if you have all the information you need or do you require a more detailed explanation on this topic?
Thanks,
Mehran Khan
0 -
yeah. thanks for the info. i have modified the code accordingly.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 695 Datastream
- 1.5K DSS
- 631 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 562 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 736 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛