No search results shown from Elasticsearch if results contains records from custom modules

[Spinwing]

Issue

We have configured two additional modules via module builder. If elasticsearch is active, when the results contains records from any of those two custom modules, the search page looks empty (no results returned).

If the search does not contain records from any of those modules then the search results are correctly displayed.

Expected Behavior

Search page should display results for all modules including custom modules.

Actual Behavior

No errors in logs even if set to debug. Simply, the result page looks empty, just the title and the standard decorations. No records or table of any sort.

Steps to Reproduce

1. Create a custom module, the simplest one is enough, in our case only the "name" field is present. 2. Create a second module, again the simplest form.
2. Create a one-to-many relationship between the two. On the second create a many-to-many relationship with Contacts.
3. Populate a record for each custom module, establish link, attach a few contacts.
4. Activate elasticsearch and ensure the index is updated (i.e. robo)
5. Run a search with a token you are sure you can find but that it does not exist in one of those two modules. Verify that the search returns records
6. Run a search with a toke you know is in one of the two modules, the search should NOT return any record, even if by interrogating elasticsearch (curl/postman, robo elastic:search) you can observe records in there.

Context

While sing SuiteCRM in a large scale database, Elasticsearch is the perfect fit to deliver fast and accurate results with enriched syntax.

This bug should be considered medium priority, as Elasticsearch is a de facto standard for high performance queries.

Your Environment

SuiteCRM 7.11.8 (latest is bugged at time of issue therefore version hold), MariaDB 10.3, Apache2 2.4.41 Elasticsearch 5.6.16 on ubuntu 19.10

[tsitle]

Maybe the PR #8513 solves the issue you're experiencing.
The current SuiteCRM 7.11.10 version has a bug that can prevent records that contain a link to a record that again contains a link to appear in the ElasticSearch search results.
Also no wildcard character ('*') is added to the search term so the search results may not contain all records you would expect.

[francescor]

is it still an issue? we are planning to use custom modules, but this would prevent us from doing so

[francescor]

We added module Project to our setup today (no custom), we added a project item, and we experience the same issue.

Any tip?