Returns the list of automatic spelling corrections 
            and/or alternative phrasing suggestions made by 
            the Endeca MDEX Engine.
            
Namespace: Endeca.NavigationAssembly: Endeca.Navigation (in Endeca.Navigation.dll) Version: 6.2.0.0 (0.0.0.0)
 Syntax
Syntax
| C# | 
|---|
| public virtual IList AutoSuggestions { get; } | 
| Visual Basic | 
|---|
| Public Overridable ReadOnly Property AutoSuggestions As IList Get | 
| Visual C++ | 
|---|
| public: virtual property IList^ AutoSuggestions { IList^ get (); } | 
Field Value
A list of ESearchAutoSuggestion objects, each of which contains a single spelling or phrased suggestion. If there are no suggestions, the list will be empty. Remarks
Remarks
            Alternative phrasing suggestions are used by the MDEX Engine 
            as the query to compute the set of matching documents returned 
            instead of the user's original search query. Alternative phrasing 
            suggestions can be returned under one of the following scenarios:
            
- The MDEX Engine's Automatic Spelling Correction feature is enabled with the Dgraph --spl command line flag.
- Alternative phrasing suggestions are requested using the NavERecSearchComputeAlternativePhrasings setter property AND the NavERecSearchRewriteQueryWithAnAlternativePhrasing setter property is used to request that the MDEX Engine rewrite the query using one of the alternatives it has computed.
- Both of the previous two conditions are met. In this case, the alternative phrasing suggestions returned will incorporate both Spelling Correction and Automatic Phrasing.
            An example of having both Spelling Correction and Automatic Phrasing 
            is if a user's query of:
             CopyC#
            is rewritten to an alternative phrasing suggestion of:
CopyC#
            is rewritten to an alternative phrasing suggestion of:
            QUERY[New Yorkk restaurants]
 CopyC#
            Here the term "Yorkk" was spell-corrected to "York" and 
            the resulting terms "New" and "York" were suggested to 
            be phrased by the Endeca MDEX Engine as "New York".
            Only those suggestions that, when issued as queries, would 
            return one or more records (before any navigation filters 
            are applied) will be returned.
CopyC#
            Here the term "Yorkk" was spell-corrected to "York" and 
            the resulting terms "New" and "York" were suggested to 
            be phrased by the Endeca MDEX Engine as "New York".
            Only those suggestions that, when issued as queries, would 
            return one or more records (before any navigation filters 
            are applied) will be returned.
            QUERY["New York" restaurants]





