We are trying to avoid creating a custom field on JobHead that stores the Salesperson linked to the order that created the job. We would like the Salesperson to flow to a job when the demand link is created, and stored in an unbound text field to get around this issue. Is this possible?
If you don’t make a place to store it then it can’t be stored there when the demand link is made.
You can use a callContext field and on every GetByID populate that from a bpm.
Just curious, What is the aversion to adding the field?
@gpayne Do you know how to set a text field equal to a callContext field?
We thought it might be better to avoid creating a large amount of UD fields that duplicate data in the system.
It would be post processing on getById like in this thread or search for bpm and callcontext.
Take this with a grain of salt as I have over 700 UD fields in my system, but I look at the data moving more than being duplicated. If you add the field to JobHead and populate it once with a bpm then that data rides for free with JobHead assuming it is not a 10,000 character field and even then whitespace is free. If you don’t add the field then every time a job is opened then you fire a bpm and then do a query to get the same data to appear on the screen. If you only wanted the sales person in a few dashboards and reports that would be different than displaying on screen.