In reply to: Arthuzad
in this case i would need both, if the fields is updated, i want to see updated value on the report and also in the form. i get it for the calculated column in the report, but i'm not sure what you mean when it needs to impact the field in the form.
Let's say we have following example:
Dictionary: People, Fields: Name, ID
Workflow: Salary Management
On some day HR created a new instance of Salary Management for new employee - John Doe, with ID 17
Few months passes, and John Doe changes last name to Doe-Foo due to getting married.
HR updates ID 17 John Doe in People Dictionary to John Doe-Foo.
Due to the fact how webcon stores the data this change will not affect Salary Management form filled in when John was employed, and on that form there will be still displayed as John Doe, same with reports.
If you have to change the display of picker value - it's not possible without changing the value of the field with new updated value:: John Doe-Foo (manually or with an action).
You could though use calculated columns on reports, or data row field on the form, which will display the data accordingly to what is currently stored under People Dictionary.
Adding to solution by Daniel - if it's necessary that's the way, but if there will be many documents in different processes/applications it might be tedious to catch them all :)