Database 1 and Database 2 are related with key value(s).
Goal: Do a report on Database 2 columns, while trying to pull in related columns from Database 1.
Assume: Database 1 has columns A, B, C, D, E
Assume: Database 2 has columns R, S, T, U ,V
Create a form with a data report tile for Database 2. Assume the cells are R, S, T, U, V. This works fine.
Now substitute for S the formula related({B}, “Database 1”). This new second cell reports correctly, but corrupts the values for cells T, U and V. They all show the first row values for every row of the report.
This has been reported before and is on the list of issues to fix.
You might be able to get it to work for now by changing the Z-order of the Text Display objects in your report (use Bring to Front on the object containing the related( function).
Playing with your suggestion, if I had just one related field, I think it would work, but I have several, so it doesn’t. I hope this can be fixed soon. Thank you.
You are correct. The key field in the second database must be just that - a field. The key in the current database (the 3rd parameter) can be a formula.
So yes, if you’re relying on a split field as a key in the database being looked into, you won’t be able to do that in a report at this time. The only workaround would be to create an additional field and fill it with the data from the other two fields. You could do this using formulafill at the beginning of the report process. When the report is finished you can either discard the field, or you could just leave it around and ignore it when not printing a report.