Search: Difference between revisions
No edit summary |
No edit summary |
||
(14 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Search works in a number of ways | Search works in a number of ways | ||
1. Email Matching | *1. Email Matching | ||
2. Manual Search | *2. Manual Search | ||
3. Parse Search | *3. Parse Search | ||
There are also 2 extra options here | There are also 2 extra options here | ||
4. Bookmarks | *4. Bookmarks | ||
5. History | *5. History | ||
----- | ----- | ||
Line 38: | Line 38: | ||
[[File:search1.jpg]] | [[File:search1.jpg]] | ||
See | |||
https://accelerator.crmtogether.com/index.php?title=Tabs_and_Lists | |||
for details on how to control what fields are displayed in the list | |||
----- | ----- | ||
Line 46: | Line 52: | ||
[[File:search2.jpg]] | [[File:search2.jpg]] | ||
This opens a | This opens a dialog window showing all available email addresses that the system can parse | ||
[[File:search3.jpg]] | [[File:search3.jpg]] | ||
Line 72: | Line 78: | ||
Using this screen you can filter the data. | Using this screen you can filter the data. | ||
When you click a record then that record will be opened in the task pane. | When you click a record then that record will be opened in the task pane. | ||
----- | |||
Customizing | |||
A. To add in a primary custom Entity* | |||
* created using the entity wizard | |||
Open the "...custompages/sagecrmws/web.config" | |||
Edit the line "SearchEntities" | |||
EG..here we add in "Project" | |||
<add key="SearchEntities" value="Company,Person,Lead,Cases,Opportunity,Project" /> | |||
Within CRM make sure that the Entity is available via webservices. | |||
* You may need to restart CRM to see the entity in the search drop down (as the config data is cached). | |||
[[File:search10.jpg]] | |||
Restart outlook or reload the app | |||
[[File:search8.jpg]] | |||
The fields searched will be the | |||
prefix_name | |||
or the table description field (if set) | |||
B. Customising Search | |||
Create a screen in CRM called | |||
ENTITYOfficeIntSearch | |||
EG | |||
casesOfficeIntSearch | |||
[[File:search9.jpg]] | |||
and add the fields you want the search data to be on. The fields you add will be added using an OR statement. | |||
Right now the following fields are used always by default using a sql LIKE statement | |||
* Company - comp_name, (comp_emailaddress also in some cases) | |||
* Person - pers_lastname, pers_firstname,Pers_EmailAddress | |||
* Opportunity - oppo_description | |||
* Cases - case_description,case_referenceid | |||
* Lead - lead_personfirstname, lead_personlastname, lead_companyname, lead_description | |||
* Primary custom entities - If there is a description field this is used and if not PREFIX_name field is used. | |||
C. | |||
If you rename an entity (for example Opportunity to Project) then you must update the user language caption for the ltem | |||
Family=Tabnames | |||
Code=Opportunity | |||
EG | |||
[[File:sage_caption_menus.png]] | |||
D. You can also use a custom view once it has the format | |||
vACSearchlistENTITY | |||
eg | |||
vACSearchlistCompany | |||
and the system will pick this up and use this instead of the | |||
vSearchlistENTITY | |||
which is a standard CRM view. |
Latest revision as of 15:45, 19 June 2024
Search works in a number of ways
- 1. Email Matching
- 2. Manual Search
- 3. Parse Search
There are also 2 extra options here
- 4. Bookmarks
- 5. History
1. Email Matching
The system will take an email and search as follows:
a. tag matching (if there is a tag in the email) b. Person match (full match) c. Company match (on domain or on person email domain returning their company) d. Lead match
If no match is found the user is presented with the new Company screen.
When there is a tag the Summary will have a yellow top.
Were there is no tag, all matches (person,company, lead) will be returned.
The first item will be shown but if you click back to the Search area you will see all results.
2. Manual Search
You can search on all available entities (this can include custom entities).
See
https://accelerator.crmtogether.com/index.php?title=Tabs_and_Lists
for details on how to control what fields are displayed in the list
3. Parse Search
This option is available under the search options menu
This opens a dialog window showing all available email addresses that the system can parse
Clicking on one of these items will use that email address in the search and act accordingly.
4. Bookmarks
This option is available under the search options menu Clicking this shows the list of bookmarks that you have made.
When you view an entity you can add/remove a bookmark from the icon.
5. History
This option is available under the search options menu Clicking this opens a dialog with the history screen showing.
Using this screen you can filter the data. When you click a record then that record will be opened in the task pane.
Customizing
A. To add in a primary custom Entity*
- created using the entity wizard
Open the "...custompages/sagecrmws/web.config"
Edit the line "SearchEntities"
EG..here we add in "Project"
<add key="SearchEntities" value="Company,Person,Lead,Cases,Opportunity,Project" />
Within CRM make sure that the Entity is available via webservices.
- You may need to restart CRM to see the entity in the search drop down (as the config data is cached).
Restart outlook or reload the app
The fields searched will be the
prefix_name
or the table description field (if set)
B. Customising Search
Create a screen in CRM called
ENTITYOfficeIntSearch
EG casesOfficeIntSearch
and add the fields you want the search data to be on. The fields you add will be added using an OR statement.
Right now the following fields are used always by default using a sql LIKE statement
- Company - comp_name, (comp_emailaddress also in some cases)
- Person - pers_lastname, pers_firstname,Pers_EmailAddress
- Opportunity - oppo_description
- Cases - case_description,case_referenceid
- Lead - lead_personfirstname, lead_personlastname, lead_companyname, lead_description
- Primary custom entities - If there is a description field this is used and if not PREFIX_name field is used.
C. If you rename an entity (for example Opportunity to Project) then you must update the user language caption for the ltem
Family=Tabnames Code=Opportunity
EG
D. You can also use a custom view once it has the format
vACSearchlistENTITY
eg
vACSearchlistCompany
and the system will pick this up and use this instead of the
vSearchlistENTITY
which is a standard CRM view.