Breaking news from around the world
Get the Bing + MSN extension
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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
As mentioned in the video I recently created (https://www.youtube.com/watch?v=GxnOdPWMYw8), since platform update 13, authorized Dynamics 365 for Finance and Operations users can create and manage custom fields without requiring development effort. Although this is documented really well in the Docs page at https://docs.microsoft.com/en-us/dynamics365/unified-operations/fin-and-ops/get-started/user-defined-fields I figured I’d put together some additional findings.
Even though we don’t have access to SQL in Production, I think it’s still interesting to see what happens with these custom fields. In the video, I added the DCO_Custom field. If we open up SSMS, we can see this actually adds the field to the ContactPerson table in SQL. Interestingly enough, it’s not normalized (like you may be familiar with seeing picklist values in D365 for Sales data.)
Custom field added in D365 showing in SQL
Additionally, our field was created as a picklist. There were some new tables added to handle this additional metadata – SysCustomFieldPicklist and SysCustomFieldPicklistValues. Querying these shows the expected combinations of which tables include which picklists and then which values each picklist has.
SysCustomFieldPicklist showing the custom field in SQL
SysCustomFieldPicklistValues showing picklist values in SQL
Interesting, though not as much if you think about the overall blueprint of the Dynamics products, D365FO now has the ability to add custom fields just like D365 for Sales and CRM had. The platforms are getting closer and closer to being in sync, and this is just one more change showing it.
The post Custom fields in D365 for Finance and Operations appeared first on Dynamic Consulting.
Business Applications communities