Search for items (Transaction:TextSearch)

In this example, we search for all items whose number or description contains the character sub-strings stop, emsschuh and dual. For this purpose, the search is initialized via the following request (URL binding)

https://b2b.beispielserver.com/?BuyersID=127654&Password=secret&RequestName=CreateTextSearchRequest&SearchString=stop%20emsschuh%20dual

or via a POST of the following, equivalent XML file.

<?xml version="1.0" encoding="utf-8" ?> <CreateTextSearchRequest xmlns="urn:veloconnect:catalog-1.1" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0" xmlns:vct="urn:veloconnect:transaction-1.0"> <vct:BuyersID>B127645</vct:BuyersID> <vct:Credential> <vct:Password>secret</vct:Password> </vct:Credential> <SearchString>stop emsschuh dual</SearchString> </CreateTextSearchRequest>

 

The search result then appears as follows, for example, i.e. six articles were found.

<?xml version="1.0" encoding="utf-8" ?> <CreateTextSearchResponse xmlns="urn:veloconnect:catalog-1.1" xmlns:vct="urn:veloconnect:transaction-1.0"> <vct:BuyersID>B127645</vct:BuyersID> <vct:ResponseCode>200</vct:ResponseCode> <vct:TransactionID>2</vct:TransactionID> <vct:StatusCode>2</vct:StatusCode> <vct:IsTest>false</vct:IsTest> <TotalCount>6</TotalCount> </CreateTextSearchResponse>

Now the search results can be retrieved.

This request

is for hits with indices 3 and 4 an (i.e. the 4th and 5th hits), more specifically, in the ITEM_TYPE format. A POST of the following XML file is equivalent.

The hits are supplied as shown in the following XML file.

 

 

Had the request made use of ResultFormat=ITEM_DETAIL, the response would have been as follows:

 

 

For ResultFormat=ID_ONLY, the following response would have been issued:

 

Related pages