Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
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
I have a basic design question, in the product entity when to use properties rather than fields ?
Hi partner,Here are some benefits of using product properties.
So, in general, when we need to descript the products like color, size or component, we use properties and fields are only used to record some unit or price list.
Hope it helps.
In addition to above, take a look at this video as well: www.youtube.com/watch
Hope this helps.
Thanks for your reply, but Is it possible to use properties as fields on a subgrid view ? I need to see all command's product on a contact form with all properties shown
Business Applications communities