Hello
If new records (for example Accounts, Contacts, Opportunities, Orders, etc.) are added to Creatio via SQL commands, they are not indexed for Global Search.
I've already tried to set the value of some fields of the new records via Business Processes but they are not indexed.
How can I force the new records to be indexed for Global Search?
Thanks
Like
Hello!
Thank you for your question.
If new records (such as Accounts, Contacts, Opportunities, Orders, etc.) are added directly to the database via SQL commands, these records will not be indexed for Global Search.
As a result, Global Search will not be able to find records that were inserted directly into the database.
To include these records in the Global Search index, a reindexing of the corresponding section is required. This process cannot be triggered manually from the user interface.
- For on-site (on-premise) clients, reindexing can be triggered via Swagger.
- For cloud clients, since they do not have access to Swagger, they can contact Creatio Support, and we can perform the reindexing for their site through a support request.
Hello Valeriia,
Doing some tests, I noticed that after creating an opportunity via SQL, if a business process updates the Owner field, the opportunity is automatically indexed and returned by Global Search. If the test business process updates for example "Created By" or "Modified By" fields the record is not reindexed. What kind of fields should be updated from a business process to force indexing of a record (for example an Opportunity)?
Thanks