I have to use the http-request activity and I dont use the configure button because it seems buggy to me. Now in properties I cannot define which authetication has to be used.
So it is necessary to build a header section in my xml that I want to send.
I figured out what is necessary that this xml contains so I want to build this xml manualy.
Now the problem:
I defined 2 variables of type System.Xml.Linq.XNamespace.
I name the first xNsSoapEnvelope, the second xNsHeaderWsse.
Now if I assign the value “http://www.w3.org/2003/05/soap-envelope” to the first variable this works without error. The value is a string!
But if I try to assign “http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd” to the second variable I get an error “cannot assign System.String to System.Xml.Linq.XNamespace”. Here is the value also a string.
But that is actually exactly the value that belongs here. See example below.
What is wrong here? Am I missing something?
Hello,
here is an example of the problem.
I used two mutliple assigns to demonstrate the diffence. Both variables get a string on the right.
Studio version 23.10.3
Used packages:
“UiPath.System.Activities”: “[23.10.4]”,
“UiPath.UIAutomation.Activities”: “23.10.8”,
“UiPath.WebAPI.Activities”: “1.21.1”
Ok, I can create an template file. But I don’t know the way to use it and afterward give the necessary values.
Remember I do not want to use Windows-Legacy!
Ok, after setting default it worked. Don’t now why that happens. But I got crasy while trying to set this value to that variable and I can reproduce that every time.
Btw. A very experienced employee recommended that I use multiple-assign when initializing multiple variables. This would be faster than individual assigns.
But you are right, if not needed they should not be used.
Kind regards
just open a new topic if further assistance is needed and share with us the XML Template along with an expected output. So we can refer on what is to fill and which values are to set dynamically.
It happens sometimes, in my case e.g. when assigning value to JObject.Item.
I did not find any specific pattern why it happens.
Usually I resolve it by cutting (Ctrl-X) the whole value and pasting it (Ctrl-V) in the advanced editor screen.
we achieved this by analyzing the malicious text within a hex editor and found out that some chars were different but differences were invisible. In majority caused by copy paste. But more investigating why / what was root causing the issue we also stopped as we just focused on the fix.
However, whenever we have doubts that correct statements are not accepted we do a fresh retype and in the past we solved most issues by this approach in little time
