Parameter content truncated

Solved773 viewsParameter length
3
0 Comments

Hi Dojo!

I have a problem with a XML response. When I get it, the content is truncated at some point and then cant be procesed. I have other XML responses working fine with smaller files. The parameter response configuration is:

<Param id="135" trending="false">
<Name>statuscode_remote/203_0_113_23/tsdb/input</Name>
<Description>statuscode_remote/203_0_113_23/tsdb/input</Description>
<Type>read</Type>
<Information>
</Information>
<Interprete>
<RawType>other</RawType>
<Type>string</Type>
<LengthType>next param</LengthType>
</Interprete>
<Display>
<RTDisplay>true</RTDisplay>
</Display>
<Measurement>
<Type>string</Type>
</Measurement>
</Param>

Whats the maximum parameter lenght in DM?

How can I manage to resolve it?

Thanks in advance!

Manuel Gallardo [DevOps Advocate] Selected answer as best 2nd August 2022

3 Answers

1
681 2 Comments

Hi Dojo,

The problem was related with the unicode content in the XML response. After adding the unicode option in the protocol type tag, the xml response is working ok.

But now I have problems with some table index, special characters are apearing instead numbers:

Any idea?

Manuel Gallardo [DevOps Advocate] Unselected an answer 2nd August 2022
Robbie Demaegdt [SLC] [DevOps Advocate] commented

Hello,

Because you added unicode to your protocol, the values in the database are being interpreted wrong as those aren’t saved as unicode.
So you will have to recreate your element and the indexes should appear normal in the new element.
Manuel Gallardo [DevOps Advocate] commented

Hi Robbie, I have recreated it and now it is working fine, thanks a lot!
You are viewing 1 out of 3 answers, click here to view all answers.