Empty ("") examine values when indexing multinode tree picker values with Examine Component

[RRmattb]

Which Umbraco version are you using?

13.10.1

Bug summary

With certain document type set up within the minimal solution. When the content models are indexed the values for one of the multinode tree pickers are filled with empty values. e.g. ([""]). It should be filled with the node name value. e.g. (["Name of Node"]).

Repo Here

Specifics

This tends to happen within a Load balanced environment. Not locally.
Umbraco support has recreated the issue, and can recreate the issue locally and in a load balanced environment.

Config used for recreating in a load balanced solution.
Load balanced config

Steps to reproduce

1. Run the solution.
2. Example content has been included.
3. Usync file have been included for this.
4. Run the Examine index on the External index.
5. Inspect the document type values.
6. Notice method field value is as described.
7. Furthermore, inspect that other single Multinode tree picker values are filled such as Subject and Type.

Expected result / actual result

Values should be filled with the name of the node. Not an empty string.

[github-actions]

Hi there @RRmattb!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂