Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
i do have a workflow that creates two different entity records (RecA / RecB), and i want to set a lookup field value on RecA to contain the value of RecB.
This should be straightforward. If you create RecB before RecA, then in the 'Look for' drop-down list of entities on the RecA form, you should see an entry for RecB at the bottom of the list, under 'Local Values'
Hi Ahmad ,
You can also do using field mapping -
Let me clarify more, when lead qualifies, it creates opportunity(RecA),and i have a workflow that creates RecB(custom entity) on creation of opportunity, now i need the lookup value of RecB to be placed on opportunity (RecA).
sorry for not elaborating enough right from the beginning.
thanks, Let me clarify more, when lead qualifies, it creates opportunity(RecA),and i have a workflow that creates RecB(custom entity) on creation of opportunity, now i need the lookup value of RecB to be placed on opportunity (RecA).
Please refer below article -
You cannot do this using oob workflow designer as there is no provision for updating 1:N entity records. Only N:1 can be updated. In the example you mentioned RecB is a lookup on Rec A which makes it 1:N from BtoA. You should leverage a custom way to do this.
As i understand you need to create a custom workflow activity. And you can achieve this scenario like Guid RecAguid=service.create(RecA);
Then assign RecAguid in lookup of RecB.
field mapping did not work in my case.
one thing can be the reason behind this issue, is it possible to make one record a child for two parent records?
Are you creating both the record at once from a workflow, if yes then you can achieve this without custom code. You need to create RecB first and then while creating RecA, set RecB from the dynamics values under local values (This would appear with teh name of step).
Even if you have are creating records separately, you could still update child records by using the Dyanamics 365 Workflow Tools -
Hope this helps.
please email me privately on firstname.lastname@example.org , i have some business with you.
Business Applications communities