Field value not available

Screenshots or PDFs of models is telling only a very little fraction of what's going on. Please export models in an archive and upload that.

But not for this one. I've seen enough from the PDF that you're calling a custom event right after the view. But where is that custom event? Triggering a custom event is supposed to be calling a custom event for each element in a list (the view result in this case), and then do something for each of them.

I saw in one of your tutorial videos that you did it this way, where you queried multiple nodes of a content type and hid the nodes based on a certain condition. That worked for me too. But here you don't need a custom event, because I only want to insert the field value of a queried node of another content type into the field of a given node. If I do it immediately after the view query, there is no result. That's why I did it after the Trigger, and it did work, but as I wrote, it only worked when displaying the message, not when entering the field.

I also tried Entity Load, but there only the ID was included in the token, so there was nothing I could do with it.

I also looked at the Get solution, and that didn't lead to any results either.

To be honest, I don't know when to use a View query, when to use an Entity Load or a Get solution, and which one is better in terms of resource requirements.

I can export the model, but it also has a View, a content type, a field, and if you import it, it will overwrite the settings of that view, etc. I did this before, I imported a previously exported ECA model and unfortunately Drupal did not indicate that all fields and views used by that ECA model would be overwritten, so I lost a lot of previous settings.

The key question is this:
I don't understand why, after the query was successful and the content of the given field was displayed, later, in the same model, when I want to insert the value into a field with a different content type, it is not available.

Using a view is needed when you want to receive a list of entities.

Load entity is needed when you want to receive 1 entity.

And when you use "Trigger custom event", that triggers a custom event for each of the entities in a list. If you use that action without an event that receives that trigger, this action just does absolutely nothing.

And when it comes to sharing information, a picture of a model looks nice, but it doesn't contain the important information. And don't worry, I'm used to work with ECA models received from users, I won't load that into my production website ;-)

Is there a way to have ECA warn you when importing that some elements (views, fields, etc.) will be overwritten?

I didn't want to take up your time, but I've been trying every option for days to solve this. In the case of Load Entity, as I wrote, I specified the ID and only got the ID back, although I obviously don't want the ID of a given entity, but rather its name, e.g. the field value, or the name of the Taxonomy.

Returning to the original topic: I would modify the previous ones so that if I put the entire view query as a token in the Display Message, it always appears, but if I include only one of the elements queried, e.g. the queried field, it no longer appears.

I'll keep trying and if I come up with something, I'll let you know.

Until then, if you think about it, suspend this topic.

Is there a way to have ECA warn you when importing that some elements (views, fields, etc.) will be overwritten?

No, but that's not required. You can export the config before importing something new and restore to that afterwards. Or, in case of ECA testing in support, just spin up a fresh Drupal site, that's a matter of 2 minutes and no risk for anything else.

When you're saying you load an entity and just got an ID, I wonder how you can know that. Are you relying on the output of a token in a message or something similar? That doesn't tell you much. If you e.g. have an entity and print that in a message, it depends on the entity implementation on what it returns as a string representation of that entity. That can simply be the ID of the entity. But that doesn't mean that the token contains just the entity. In fact, if you use the load entity action, you either get an entity or nothing. But you never get an ID.

If you're uncertain about what values you have and what steps your ECA model takes when you execute it, you can only rely on the debug techniques described in the ECA guide. Printing messages on screen doesn't help ion such scenarios.

Changing status until we gt feedback about further test results.

I haven't reported anything since then because although there have been results, new things have also arisen and I don't want to bring up so many problems, so for a while now I won't be submitting any questions, requests, or bug reports and burdening the developers with them.