Hello !
I am trying to set a simple process workflow, to populate 'Lead Source' from the opportunity to a similar field in the appointment, as soon as the appointment is created. The process is definitely running - since, if I enter some data in the target field, it overwrites - but with blanks, ie, it is unable to fetch data from the source field. To map, I have used the Regarding(Opportunity) and then mapped to the 'lead source' field. A similar approach in other entities is working. Question is what are the reasons why such a look-up may fail to fetch ?
Done - tried again all possible combinations. Despite mappings in place, the records are neither getting 'auto populated' nor are they responding to a process workflow (returning blanks). I suspect some technical issue in instance. Have raised support ticket.
Meanwhile, if anyone else has any thoughts / tips / similar experience, appreciate few pointers.
Actually that is what is exasperating - the requirement seems quite simple, but without having to replicate multiple mapping, there seems to be no simpler way across - and this is where I tried to make a combination of mapping and process - probably ended up with a mess, like you pointed out. So if I keep the process out, and go only with mapping, to get titles and address of customer in Invoice, are you saying I need to carry these fields from Contact to Account and then again from Account to Invoice ? ('Primary Contact' and 'Secondary Contact' is defined in Account, so can't have direct Contact to Invoice map). I am sure there must be a simpler way... As a relationship, the following is what I am trying to achieve-
Contact A >>>] [>>>>>Invoice X
Contact B >>> ] Account M [>>>>>Invoice Y
Contact C >>>] [>>>>>Invoice Z
At each stage - Contact / Account / Invoice certain templates are generated, that need to populate the cross data across the three entities. I feel something fundamental is missing out...
Hi,
You requirement is pretty common and can be achieved by mappings or using workflow. I think the problem in your case is the trigger point.
The relationship mapping only works when you create a record within the parent record via subgrid.
The workflow has its on trigger like create/ update of specifc field etc.
Based on what you have written, I think you are trying to many things at a time and getting confused. Deciding on which one to use (Relationship mapping & workoflow0 depends upon your requirement but workflows are preferred as it will trigger based on the trigger you have selected unlike the mapping which works on only create.
I would suggest to check your workflow triggers and see if the primary & secondary fields r selected?
Again, it is a very simple requirement, take a break and start fresh :)
Hope this helps.
Thanks Ravi. The sequence check for 100000000 was a good tip - though I checked, my settings are in sync.
My understanding is, once fields are mapped (either auto by system, or manually by matching to like fields across entities), the data can then be fetched by a process to populate even a non matching field such as text. This function however seems to be inconsistent.
In the above case, while re-checking, I realised a wrong mapping, which when corrected, is populating data automatically even without a process ! Perhaps something fundamental I have incorrectly understood on mapping and fetching (lookup) of data ?
Example:
A contact is pegged as primary or secondary in Account. Against Account, invoices are raised. I want to fetch salutation of customer in Account (and then later in invoice). Even through the relationship is maintained, the auto populate does not happen, and process led populating returns blank. (I hope you don't mind I will share this setup instead, for your shedding some light?)
Relationship mapped : 1: N Contact to Account (Referential), Salutation manually mapped.
In account_primary_Contact, there are no mappings (only system).
For secondary contact (new_contact_account_SecondaryContact), the manual mapping of two optionset fields is :
... and then published. Since primary does not show mapping option, not much I can do there - i assume system can show.
Now when i tag two contacts in account against primary and secondary, the mapped fields do not automatically populate the data. So created a process as :
The 'Title Primary' and 'Title Secondary' are simple text fields, as process does not allow reference update in optionset / lookup fields (or does it?!)
Now the process run just does not pick up the values for title in account.
I am imposing a long thread on you - grateful if you can guide. Have spent zillion hours now in trying to address this one last bit of mystery left before taking go live. Huge thanks !
Hi,
If you are sure that the workflow is running and the field contains data then it should populate. It is also possible that the workflow is updating the field but then there is some other process which is overwriting the same field again.
Other reason could be (assuming lead source is an optionset) that the value behind the options for the lead source doesn't match between the entities E.g. in Opportunity you have a Lead Source options as "Website" with value as 1000000 but in appointment there is no option with the value as 1000000.
Please check these, if it still doesn't resolve, please share the screenshot of your workflow and field properties of lead source from appointment & opportunity.
Hope this helps.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156