Forum Post: RE: Mapping multiple Datasets/temp-tables to one REST call

[knavneet]

So, the REST Adapter receives null for both dsFormdata and ttReportOptions. Since you have mapped these parameters together in an HTTP body under node names “dsFormdata” and “ttReportOptions”, your JSON input must be wrapped inside a “request” node. Something like this: === { “request” : { “dsFormdata”: { “dsFormdata”: { …} } } } And { “request” : { “ttReportOptions”: { “ttReportOptions”: { …} } } } ==== I have had experience get NULL in REST Adapter because I missed creating the JSON payload wrapped inside a “request” node. Can you check if that is the case with you too. From: RWEBSTER [mailto:bounce-stigdarkstar@community.progress.com] Sent: Tuesday, December 16, 2014 2:37 PM To: TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] Mapping multiple Datasets/temp-tables to one REST call RE: Mapping multiple Datasets/temp-tables to one REST call Reply by RWEBSTER Hi knavneet, Yes the error I'm seeing is in the appserver logs. The REST logs show that the parameters are being passed across as null: 2014-12-16 08:53:50.601 [DEBUG][REST] Param name: dsformdata 2014-12-16 08:53:50.601 [DEBUG][REST] Param type: 36 2014-12-16 08:53:50.601 [DEBUG][REST] Param ordinal: 4 2014-12-16 08:53:50.601 [DEBUG][REST] Param mode: 1 2014-12-16 08:53:50.601 [DEBUG][REST] Param value: Null 2014-12-16 08:53:50.601 [DEBUG][REST] Param is extent: false 2014-12-16 08:53:50.602 [DEBUG][REST] Param extent: 0 2014-12-16 08:53:50.602 [DEBUG][REST] Param has Before Image: false 2014-12-16 08:53:50.602 [DEBUG][REST] Param name: ttReportOptions 2014-12-16 08:53:50.602 [DEBUG][REST] Param type: 15 2014-12-16 08:53:50.602 [DEBUG][REST] Param ordinal: 5 2014-12-16 08:53:50.602 [DEBUG][REST] Param mode: 1 2014-12-16 08:53:50.602 [DEBUG][REST] Param value: Null 2014-12-16 08:53:50.602 [DEBUG][REST] Param is extent: false 2014-12-16 08:53:50.602 [DEBUG][REST] Param extent: 0 2014-12-16 08:53:50.602 [DEBUG][REST] Param has Before Image: false This tells me that the JSON I'm providing is incorrect (or I'm providing it incorrectly). I've double checked and the JSON is valid JSON, and when parsed the structure looks like I would expect. I'm at a bit of a loss as to where to go from here. Thanks Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...