Hi,
What I can see from the attached screenshot is that the format of the end_time in the simulated request differs from the format in the recorded request.
Could this difference cause the exception on the backend that was received in the response?
Hi,
Thanks for the reply. The issue raised when I use parameterizing the value and replace it with the variable.
I seen on the doc's that the loadcomplete send binary xml when doing the parameterizing - anyway we can
still use and send the xml document as per we are doing in the record?
Thanks.
Hi,
Not sure I completely understood what you are asking about...
When you do parameterization, you, basically, create some variable, populate it with some value and command LoadComplete where to use this variable.
Note, that LoadComplete has no idea about what values can be used for this or that variable and what values cannot. The only thing it (LoadComplete) does is that it modifies request by inserting the data from the variable where specified, sends the request and compares returned result code with the recorded (expected) one.
Without knowing more details about your case, my understanding is like this:
-- You created some variable and somehow populated it with the date/time value;
-- You commanded LoadComplete to use the value of this variable for the end_time parameter.
It appeared, that the format of the variable's value is different from the value used in the initially recorded request. It looks like that this difference caused a failure on the backend.
What I would try is to assign the variable exactly the same value as was recorded initially and check if the request pass or still fail.
thanks again for your reply, i did exactly sending same value on recorded and simulated request body using parametization and still got same error. Actually we are doing REST and sending XML just for the record.
see attached image below..
Hi,
> Actually we are doing REST [...]
Well, maybe in this case you should pay attention not only to the body of the request, but also to its header?
If you don't mention anything suspicious in the request header, I would use some tool like Fiddler to record the actual traffic sent by LoadComplete and investigate it (maybe together with developers). I think that it is quite possible that you cannot change just body data, but must do it synchroniously with the data in the header.
As the last resort :) you may consider creating a Support case via the http://support.smartbear.com/message/?prod=LoadComplete form.
