DEC 20, 2018 | 04:52PM EET
James replied:
Hi Ahmad
OK, I have figured it out, I think this explains
- T1: a flat data table, containing d1, d2 and d3 data bits
- T2: table containing one text field d4, a lookup on d1 (of T1) and 2 auto fields based on that lookup, ie d2 and d3
- T3: table containing one text field d5, a lookup on d4 (of T2) and 2 auto lookups based on that lookup, ie d2 and d3 (from T2)
In essence
- that all works fine if I keep the render order, d4, d2 and d3 (importantly, the manual lookup field comes first)
- but, say d2 comes before d4, then it renders the T! Primary ID for d2 (the issue I noticed)
A workaround I used, because render order was important
- I placed my manual-lookup field before the data, and hid it in the table view
- I also placed the same field as a auto lookup in the position I wanted it rendered (with a slightly different name), and hid it in that data view
I don’t need further help, it may be worth putting this on the community forum – where as the problem seems obvious with this sanitised data, it was hard to spot in the real situation.
Thank you for your assistance – loving AppGini, well done. Hoping the reports work out as well as the data input
Very best,
James