Timeline for Filtering Approvers in SOAP retrieve request
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 8, 2014 at 21:55 | vote | accept | Eliot Harper | ||
Aug 31, 2016 at 22:18 | |||||
Mar 8, 2014 at 21:55 | comment | added | Eliot Harper | We are parsing the SOAP response and filtering where Role.CustomerKey equals APPROVER. We're actually doing this by transforming the XML response to JSON, but it could be also achieved by XSLT. | |
Mar 7, 2014 at 13:53 | comment | added | Kelly J Andrews | Would you be sure to add as an answer what you eventually did do, and then mark this as answered. Thanks for your help! | |
Mar 6, 2014 at 4:14 | comment | added | Eliot Harper | I eventually received a response back from ExactTarget and they explained that it's not possible to filter where Role.CustomerKey equals APPROVER at this time. | |
Feb 6, 2014 at 1:30 | comment | added | Eliot Harper |
Hi Kelly, that does not work either. It returns <OverallStatus>Error: The Filter Property Roles.Role.CustomerKey does not match with the fields of the view</OverallStatus> . I'll escalate this through the channel and let you know what the solution is.
|
|
Feb 5, 2014 at 17:19 | comment | added | Kelly J Andrews | I thought I corrected both sides of that copy paste :) I am guessing you also tried Roles.Role.CustomerKey? I have no idea if that works, I so rarely filter on sub-nodes. | |
Feb 5, 2014 at 17:14 | comment | added | Eliot Harper |
Hi Kelly, thanks. I have just tried this now (note I fixed your filter value to <Value>APPROVER</Value> ) but this returns error: <OverallStatus>Error: The Filter Property Roles does not match with the fields of the view</OverallStatus> . Perhaps this is because we have an array of roles? You can view the result without filter if that helps.
|
|
Feb 5, 2014 at 11:42 | history | answered | Kelly J Andrews | CC BY-SA 3.0 |