monthly revenue. In a data export of Users, normally the only field included from the Store would be the Store's unique ID. We can include each User's Store's
monthly revenueon a second
monthly revenuefield on the User object. That field will also be included in the CSV export. However, the User's
monthly revenuefield will also need to be updated each time the Store's
monthly revenuefield changes. Using a data trigger here would make since if a User can make changes to a Store's name in multiple places in the app.
do a search for Items:countcall in each row and calculating the number of items, a number field named Item Count can be recalculated each time an item is added/removed. Again, this makes most sense if the number of items can be changed in many places in the app. If it is only changed in one workflow, you can add the step to save the number of items on the User object inside that same workflow.