@darrenhillconsulting the only way I got something like this to work was to include the value in the dataset you’re passing to the map/reduce steps. In my use case I had to log activity to a custom record which meant getting the custom record id when it first creates it on the getInputData stage and then updating the custom record using that custom record id on the summarize stage.