Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have an 'office' lookup on a custom entity that's created quite often by our users.
Most of our users will always use the same office when creating this record and I was hoping to add the same 'office' lookup to the systemuser object with a mapping to set the 'office' lookup on custom entity to that of the user creating it, but when I go to the N:1 relationships, I don't have an option to create mappings between the custom entity and the createdby user.
The most suitable solution is to use Flow.
First of all, we need to know whether your D365 is online or OP, because Flow only supports Online environment.
Sorry, I should've said - we're on-premise, so Flow isn't an option.
If not, it would seem to be a missed opportunity, not being able to set per-user-default-values for fields.
I would recommend you use workflow.
Go to Settings > Processes, new a workflow for custom entity.
Start When: Record is created. Scope: Organization.
Update the custom entity record. Use Create By (User)'s office lookup field value to populate the custom entity's office lookup field.
Thanks for the suggestion on workflows, Hao. But a workflow will only run after the user clicks save. Sorry I wasn't clear in the OP, but I'm looking for a solution to set the field when the form loads, rather than on save, similar to the relationship mapping functionality.
While users will usually set the field to the same value (hence the desire to default it for them), they'll sometimes need to set it to a different one. So the goal is to default the field to their usual office, while still giving them the opportunity to change it if needed.
I appreciate I can set the workflow to set the field only if they leave it blank, but we want to give them the visual reminder of what it will be set to by default.
Business Applications communities