on 09-02-2010 4:36 PM
Hello Gurus,
did anyone got the Incident Managent long text search working that was introduced with SP23 (I think)?
I followed all the SPRO configuration steps. I have a up-to-date TREX hooked up and running.
The compiling of CRM_OBJECT runs fine. I did not do any further steps as I expect the long text search to work now.
But I either find no Service desk tickets (if I use a search term that isn't included in a ticket) or ALL tickets (if I use a search term that should result in f.e. 1 hit).
If someone got it working, I would like to share experiences, since the documentation is pretty poor.
Hi,
I configured long text search function and it's working fine on SP24.
What I did is:
a. SPRO configuration under "Full-Text Search and Solution Database"
b. Add a delta compilation action to an action profile. This is because I'm using Z- transaction type and Z- action profile.
c. Schedule delta compilation job.
d. Add a parameter "SMWORK_INCIDENT_MAN_TREX" to table AGS_WORK_CUSTOM.
e. Create a new query for TREX long text search.
I think these are the same as what you did...
Regards,
Kazuhisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kazuhisa,
thank you for your response. My problem remains the same.
What I didn't do when setting up the Long Text Search is your Step:
d. Add a parameter "SMWORK_INCIDENT_MAN_TREX" to table AGS_WORK_CUSTOM
I tried it out with no effect on my query. Still no or all messages as the two only possible results.
Where did you gather the information about this parameter? In my SPRO nothing is mentioned about it.
Maybe it is an issue with SP23. I really don't know what to do....
Hello shivjansi,
I implemented Note 1481794 - without success. In SAF, all my lights are green. If I got to the Webservice Indexes, I can compile my CRM_OBJECT with success and 1400 Entries afterwards.
Also the search works in SAF.
How else can I verify that my TREX is working correctly?
Thank you all for your help!
The question is still standing....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Spaggi,
As long as the mentioned parameter can be found in table AGS_WORK_CUSTOM, it will bypass checkings for search engine, index, etc...
I suggest you to fully remove the entry from AGS_WORK_CUSTOM.
After that, Solman will only use TREX search when related TREX/SAF checkings end in success.
In case of failures, error messages could be more specific.
Thanks & Best Regards,
David
Nobody?
Edited by: Spaggi on Sep 6, 2010 9:03 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.