Question3Replies33Views CharlesG14 Member since 2017 11 posts EIA Posted: April 27, 2017Last activity: April 28, 2017 Closed Anomoly with setting value in a case and readingI have a report definition that reads data after an activity is called(runs data transforms that eventually set a property's value in the case).It seems to not read values set until after trying a second time while in the case. Works when I run the report definition directly.Maybe it's a caching issue.This is the scenario.1. I click a row of data.2. That click starts an activity.3. The activity, takes the selected value and sets the value via a data transform.4. The value is stored in a property of the case5. The report definition is supposed to read that property and filter using it.I get all the data on my first click of a row.My second click seems to actually get the value. Reporting User Interface ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoMarcLasserre_GCS PEGA replied to CharlesG14Hello, Do you have commit between your data transform and the report definition ? I guess you will need to have one if the report definition is looking at the DB details. Posted: 3 years agoSantanu PEGA replied to CharlesG14Have you tried tracing the events ? Are you seeing any delay in the sequence of events ? Also adding an extra step to make the activity deliberately wait ( using something like thread.wait() ) can also help. Posted: 3 years agoCharlesG14 EIA replied to CharlesG14Thanks for the responses, I will try to see if these work for me.