Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
What happens if an exposed table is changed?
The WSDL for a service does not change automatically as a result of making tailoring changes such as adding a new field to a table. Only if you include the new field in the Web Services API by adding it to the extaccess record will the new field be exposed.
If you change the caption (alias name) by which a field is exposed in a Web Service, you are going to have to modify and recompile any SOAP client applications which reference this field. You can rename the internal Service Manager field names, even for fields which are exposed via Web Services, without impacting deployed Web Services, as long as you do not change the alias name by which the field is known to Web Services.
Finally, if you add a new field, make the new field a required field and you have previously deployed Web Services applications which do not populate this field, you must provide tailoring in the server to generate a valid default value for the field when a value is not provided. Otherwise, inserts and updates via Web Services will fail because the new field has not been populated when the record goes through validation.