- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2022 03:32 PM
I have created text index, generated index on the tables and added the tables as source in the portal. As well as in system definition->Dictionary have set 'Text Index' attribute to true for these tables where type is 'Collection'. System Scheduler-> Scheduled Jobs text index events process is also configured.
Search on the portal is working fine in development.
But when deployed update on test instance, search is not working. Verified on the test instance, all the required objects are deployed on the test instances.
Do text indexes have to generated on test instance manually?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2022 12:15 PM
Hello mkm,
Yes, text indexes need to be generated in each instance. Same occurs if you clone your instance.
Here is official documentation about text indexes:
Here we can read:
Note:
New tables created by update set transfers have text indexing disabled, even if it is enabled for the tables included in the update set.
Considering this, you need to rebuild your text indexes in the test instance.
Please mark my answer as correct and helpful if it is relevant for you.
Best Regards,
Filipe Cruz

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2022 12:15 PM
Hello mkm,
Yes, text indexes need to be generated in each instance. Same occurs if you clone your instance.
Here is official documentation about text indexes:
Here we can read:
Note:
New tables created by update set transfers have text indexing disabled, even if it is enabled for the tables included in the update set.
Considering this, you need to rebuild your text indexes in the test instance.
Please mark my answer as correct and helpful if it is relevant for you.
Best Regards,
Filipe Cruz