ContributionsMost RecentMost LikesSolutionsRe: BUG? For nodes containing @ JSONPath Match works differently in SoapUI and SoapUI NG After upgrading to Ready!API 1.8.0 the problem was not reproduced. Thanks. BUG? For nodes containing @ JSONPath Match works differently in SoapUI and SoapUI NG We have names of the id fields starting with "@" char and each item created has existence check on that field. JSONPath: $.bean.@id Expected result: true In Soap UI Pro 5.1.2 the "Select current value" function auto-completes with "true". In Ready!API 1.7.0 SoapUI NG the same operation auto-completes with "false". Also, the test steps from the test cases that are following are using the ID value. Using "Get Data" option, the @id element can be selected from a previously executed step but when executed it is resolved to null value. For example, having a POST that has ($.bean.@id) in response, followed by a GET that uses the id: (${POST - addItem#Response#$.bean.@id}) will result in executing the request: GET http://localhost:6080/rest/v1/application/.... /item/null HTTP/1.1 Is there a workaround for this issue? Thanks, Ionut Solved