Looks like your comment went missing when you submitted this, can you please describe your use case and the request in a few sentences? I'll make sure to get back to you with answers afterwards.
Odd - not why it didn't save. I have been using the new feature that can pull in account fields (and other object fields) in the call. It has been very helpful. I would be great if the opposite could be done. If a field is updated on a call, push out the value to a designated field on a different object. We have had to do this a few times in the past so we've worked around it but it would be nice to have a canned feature like the Call pull in feature. thanks
Thanks Kathy, can you please share what exactly are you looking to update and in which case? I'm thinking about Save vs. Submit and also what else would potentially drive this push and to which application area?
Can you please also share some details about how you solved this in the past?
For my clients, it has only been the account object where this type of thing has been requested.
An Example - Our client had a sales continuum pick list on the call where the user was required to record where they felt the account fit. They wanted it on the call so they could see, over time, the movement within the continuum. On the account they wanted to be able to have a read-only field that held the value from the last call. This was being done for easier viewing for the rep and to simplify reporting. If I remember correctly, we used a trigger to copy the field to the account on call submission. Of course there could be a few potential logic issues based on the date of the last submitted call. I don't recall if/ how we accounted for that. My guess is we stored the date of the last submitted call on the account for an easy logic check. I guess a batch process may have been a better approach. I'm not a developer so forgive my naivety.
It would just be nice to have a canned way to do this similar to the way you implemented the call pull in fields.
Thanks Kathy, as with your example as well, these scenarios and the related needs are usually very different for each implementation and for the most part they can only be solved with customizations, specific to the exact use case.
With that being said, we'll be on the lookout to identify commonalities and will provide feedback here if and when we will consider this for a potential future enhancement. Please keep following this topic for updates and thanks again for your feedback!