Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Why would you use C# to create entities, attributes, entity relationships, and many of the other customization's that are traditionally done in the GUI in solutions. My understanding is best practice is to create this kind of stuff in a solution so you can export from a dev environment and import into a production environment. Even my limited reading about ci/cd they seem to take the solution approach using powershell to deploy solutions. Am I missing a common use case for this?
I'm guessing those examples are just for expository purposes. I can't imagine a reason for doing it by code.
Now views (savedquery) that extend beyond the Advanced Find designer capabilities -- that's a different story.
The benefit of using C# to create these things is that you can quickly connect to an instance and create all of the components included in the code. This can be a lot quicker than manually exporting and importing a solution. You also benefit from all of the features of the C# language and can choose create components conditionally.
Not sure how common this use is, but I use this API for importing customisations from Excel spreadsheets
Basically I have a feature in an app where I define entities, fields, picklist options etc. within spreadsheets. The app reads the customisations in the spreadsheets and creates the customisations for me via this API. This has saved me a lot of time by avoiding having to create fields and picklist options one by one within the web user interface when there is a large volume of customisations
Again not sure how common this is but answers your questions in terms of a use case for this API
Sounds like a good idea to me. I have spent way to much time creating optionsets for states and countries that could easily be created once and reused using the method you are describing.
It is helpful when you are creating a product or have all entities and attributes in a spreadsheet.
You can write an application to import spreadsheet that create entities and attributes.
Business Applications communities