Regarding dereference expressions two dereference or one dereference?

[Pointer]

Regarding the Dereference property, which has the same function in terms of configuration;

[Column2] = [ID1]. [ID2]. [Column1]

[Column2] = [ID2]. [Column1]

When I use both, I get the same result. My question is; Is it correct ([ID1]. [ID2]. [Column1]) or a [Column2] = [ID2]. [Column1] file. In short, which one to use in terms of the right speed and configuration.

[Steve]

Why would you think to use [ID1].[ID2].[Column1]?

[Pointer]

I guess I couldn’t express

Table 1:  [ID1]...[Column1]
        Table 2 : [ID2]...[ID1] (Ref)
             Table 3: [ID3]...[ID2] (Ref)...[ID1] (Ref)....[Column2]

[Column2] in Table 3 is an equal value to [Column1] in Table 1. I have 3 tables and they are related in this way one under the other. Is it better to get data from table 2 or table 1 to “[colum2]” column in table 3? When I want to get this value in Table 3 what is the correct statement?

[Steve]

This makes absolutely no sense to me.

[Pointer]

I got the same results in the performance test I did, it didn’t change much. There is no problem in data entry, either.

[Marc_Dillon]

I’m wondering the same thing as Steve. How did you even think to do that?

I think I’m gonna use this expression for now on whenever I want to reference a column’s value in the current row:

[_THISROW].[id].[id].[id].[id].[id].[id].[id].[id].[id].[id].[column]

It just feels right.

[Rifad]

[Marc_Dillon]

The shortest path is generally the best.

[Pointer]

I did not want to open a new topic. I want to ask a similar question. There is a main table and a child table attached to it. From the records I added to the child table, I take the last record I added to the main table with “maxrow” with a normal column and update the related rows with workflow. I can do the same by using virtual columns without using a workflow. Should we use normal columns and workflows, or should they be updated with virtual columns?