GetAlarmDetails API Method in version 10.3.0.0-14100-CU13

Solved78 views
0
0 Comments

hi, I'm having problems using this method "GetAlarmDetails" on this DMa version 10.3.0.0-14100-CU13. Every alarm that I try to get the details I receive the same response: "<soap:Text xml:lang="en">Error trapped: DMAService Error: Invalid parameters. Invalid alarmId and / or dataminerId.</soap:Text>"

This behaviour doesn't appears on 10.4.0.0-15151-CU9, our development environment. Is this a known bug issue or I'm missing something?

thanks!

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 2 days ago

1 Answer

0
9.48K 3 Comments

Hi Jesus,

This error means that the dataminerId and/or the alarmId are < 1. Before 10.4.0[CU8] this would throw an error, which is what you are seeing here. Since this version, there have been internal changes that have made this check redundant.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 2 days ago
JESUS PEREZ-ARANDA commented

Hi Wout. I never use an alarmId or DmaId <1. Here is an example:

<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd="http://www.w3.org/2001/XMLSchema&quot; xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"&gt;
<soap12:Body>
<GetAlarmDetails xmlns="http://www.skyline.be/api/v1"&gt;
<connection>52d0d41f-938f-4ed6-bb68-489ea07d993c</connection>
<dmaId>6310</dmaId>
<alarmID>264070967</alarmID>
</GetAlarmDetails>
</soap12:Body>
</soap12:Envelope>

And the response:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Receiver</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text xml:lang="en">Error trapped: DMAService Error: Invalid parameters. Invalid alarmId and / or dataminerId.</soap:Text>
</soap:Reason>
<soap:Detail/>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Wout Mahieu [SLC] [DevOps Catalyst] commented

Hi Jesus,
It seems like the 'dmaId' parameter in your example is incorrectly capitalized. The parameter should be called 'dmaID'.
JESUS PEREZ-ARANDA commented

thanks Wout. it works!!
regards
You are viewing 1 out of 1 answers, click here to view all answers.