AlumniHi aaronpliu,
Unfortunately, currently, there is no way to add both values: a parameter and header if they have the same name. We have a corresponding feature request to improve this behavior.
In the meantime, you can add your Header parameter as a header in the "Headers" tab:
Thanks Nastya_Khovrina .
Yes, I can add "parameter" in Headers tab and do it for other parameter, like "Cookie", "Content-Type"...etc.
However, all of parameters are shown in "Request" panel with different "style and level" when import endpoints, right? Style for "Query" as query parameter, "TEMPLATE" is part of path, "Header" is for request header... I always need to take "parameter" (style is "TEMPLATE") and ignore "parameter" in Header if they are the same name.
"parameters" in request panel are "Custom Properties", "Headers" tab are another key-pair. What's difference for them?
Anyway, how can I update definition and don't worry about missing "parameters" if there are the same?
I can hardly update them and have to manually maintain definition change in SoapUI. That is not expected behavior, there are so many test cases created and referenced those endpoints already.
Thanks,
/Aaron
AlumniHi Aaron,
There is no difference between the "Header" parameters and headers which are defined in the Headers tab.
Unfortunately, there is no workaround except for the provided one.
Thanks Nastya_Khovrina .
Let's skip the topic of parameter of Header.
Can we talk about definition update? I don't know why definition was not updated even if I changed source file?
I manually copy the source file (.json) from server, and put it in my local. as conflicted parameter name (said above), I had to remove one, and updated definition in SoapUI. the changes were not reflected in SoapUI, and seems it keep the same as before.
Did you repro such issue?
Thanks,
/Aaron
AlumniHi Aaron,
To reproduce the issue we will need your old and new definition files.
Also, please clarify what changes were not reflected.
