Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
anyone has any idea why the quick create form is not showing up even though i enabled the setting.
would you mind to double confirm, you have enabled the setting, and the quick create form is created also?
I am pretty sure those setting are enabled. Perhaps i elaborate more, this quick create form doesnt work when i want to create the record through parent form.
you can try to follow the below steps to verify.
1. Make sure the "Allow quick create" is checked.
2. Make sure Quick Create form is created.
3. Now you should check the parent lookup field in your child entity, in order to use the quick create form, the parent lookup field in child entity must be set as "Business Required".
thanks for solving my problem
Step 3 is what solved my identical problem. Thanks!
Even after making above changes, quick create works for the very first time and second time when i try to create quick create form is not loading properly.
i need to refresh the Parent form and then try creating the second child record using quick create form. Any idea on this?
Kiranmai - That's a known bug with the newest version of Chrome. I thought it was fixed for online instances, but maybe not all of them? Definitely not fixed for on-premise. If you search on the forums there are a couple of posts that talk about this, and give a workaround if you're on-prem and really need it working right with Chrome.
Business Applications communities