Svetlana
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
How to use GetData in SQL in DataSource
Hello, I'm trying to use GetData in SQL Query. If I use an expression ... WHERE Column1 = “${TestStep1#Variable1 it errors out: Parsing error. Failed to parse SQL query. Invalid SELECT statement. Unexpected token ‘{’ at line. If I use an expression ... WHERE Column1 = “${PreparedProperty1#Variable1}” it errors out: Can’t get the connection for specified properties; com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name ‘${PreparedProperty1#Variable1}’. How to use GetData in SQL in DataSource?1.3KViews0likes1CommentRe: Switching to Form view and back to XML view deletes field tags that were blank.
Hi Tanya, Thank you for your prompt reply. I installed the maitenance build using the link you provided. After installation an instance of regular Ready API was launched automatically. I encountered absolutely the same issue as I described yesterday. Structure <abc: State></abc: State> didn't make any difference. This tag was deleted anyway. Then I manually ran another instance of Ready API Snapshot from Windows menu. The behavior was slightly different: an Error showed up with following text: Do you want to recreate a default message from the schema? I clicked No and all the fields dissapeared from Form view but xml file wasn't blanked out. Running my service created an error. Then I closed current Ready API Snapshot instance and launched another one. This time I answered Yes to the error message. It set all the fields to "?" value but kept the structure in both Form and XML views. I think I will stick with regular Ready API rather than Snapshot. If I don't switch to Form view, Ready API allows me to run services based on an XML file.3KViews0likes1CommentSwitching to Form view and back to XML view deletes field tags that were blank.
My XML file contains following structure: <!--Optional:--> <abc: State/> <!--Optional:--> <abc: PostalCode/> <!--Optional:--> <abc: Country/> After switching to Form view and back to XML the same area looks like that: <!--Optional:--> <!--Optional:--> <!--Optional:--> Is it a bug?3.1KViews0likes8Comments