Calculated fields do not update if fields are on different tables

Issue: Calculated fields do not update if fields are on different tables.

---

$issuedisclaimer
Version Found: 19.2

Steps to Reproduce

1. Create a new database
2. Create a date field in the database (Date1)
3. Create a calculated field (Calc1) that counts the number of days since the date in (Date1)
4. Keep creating new fields until the fields start to get generated on a spill over table
5. Create a second calculated field (Calc2) that counts the number of days since the date in (Date1)
6. Add todays date in Date1 and click save, check the number in Calc1 and Calc2. They should both be zero
7. Either wait until the next day or change the system date to the following day
8. Log into Act and check the values in Calc1 and Calc2

Actual Result:
Calc1 will show '1' as expected but Calc2 will still show '0', it doesn't matter if you try to force a refresh (F5) it still shows '0'

Workaround:

You may be able to work around this by creating two new fields to use as the Calculated field and its data source (without deleting the existing fields) to try to force both fields to be on the same table.

From there you can add the new fields to the layout and copy the source data from the old field to the new field.

Once the new Calculated field is set up with the other new field, the issue shouldn't occur anymore and the old fields can be removed.



Reference#: D-07097
Status: Open