Cross Doc Actions - Date not being recognized

[Hannah_Krumholz]

Hi!

I am doing a cross doc action where I add a row back to my original table. I have two look up columns in both tables. When I add a row via the cross doc action for some reason one of my look up values isn’t recognized. Any ideas why?

Cross Doc’d Row:

Original Table w/ Cross Doc’d Row - not recognizing 5/31/21 as being in the lookup column:

[Jean_Pierre_Traets]

Dear @Hannah_Krumholz,

Not sure, but I assume that you are not aware that the cross doc is a single direction sync

All the information in your cross doc table has become a static copy of the original.
In the cross doc columns, there is no lookup connection to the original source table.

Other community members with a wider “cross doc” experience might be able to advise you better

[Hannah_Krumholz]

Thanks for the reply!

I am using Cross-Doc Actions in order to send information back to my original doc.

Similar issue to this person:

Bug - Cross Doc Actions - AddRow sending Text not Row

I am using CrossDoc action AddRow() to create a row in a table. I am sending an row value back to the table lookup column, which is what a lookup column would expect. But instead of the receiving table getting the lookup value, it is getting a text value. For example I have a column [Unit]. This has kg, L, cm, ea as values. I use the CrossDoc AddRow() to send (ea) (parens meaning a the Unit row value) but instead text arrives. This makes things break because the referencing formulas don’t work…