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
If you’ve been following, I had a series of Client API posts late last year. Below I have regrouped the new Client API functionality in a table for reference. This can become helpful especially if you are developing with the “old” CRM 2011 mindset to easily see what you can achieve differently and/or more efficiently in CRM 2013. Details on the new functionalities is available on the Microsoft Dynamics CRM YouTube video and in the CRM 2013 SDK.
Method and Syntax
Asynchronously refreshes and optionally saves all the data of the form without reloading the page.
You can pass a callback method to execute on success or error
See my blog post on this here
Returns a Boolean value indicating if the form can be saved or not
Set the form as dirty
Gets a string for the value of the primary attribute of the entity.
Xrm.Page.ui.setFormNotification(message, level, uniqueId);
Use setFormNotification to display form level notifications and clearFormNotification to remove notifications. Gareth Tucker has a great article on these here.
See article linked above for details. Notifications can be set at the field level
This method is used to override the field’s precision
Specify whether a date control should show the time portion of the date.
Specify whether a date control should set a value including the entire day.
Use add additional filters to the results displayed in the lookup. Each filter will be combined with any previously added filters as an ‘AND’ condition
The entity logical name is optional. If this is set the filter will only apply to that entity type. Otherwise it will apply to all types of entities returned.
Use this method to apply changes to lookups based on values current just as the user is about to view results for the lookup.
The argument is a function that will be run just before the search to provide results for a lookup occurs. You can use this handler to call one of the other lookup control functions and improve the results to be displayed in the lookup.
This API call is used to remove event handler functions that have previously been set for the PreSearch event (see above)
Returns the name of the current user.
See my blog post about it here
Displays a dialog box containing an application-defined message.
Displays a confirmation dialog box that contains an optional message as well as OK and Cancel buttons.
See additional notes on this here.
Determine if an entity is an activity entity.
Opens an entity form. Parameters are optional and used to pass the form ID, set default field values or pass custom query string parameters
Opens an HTML web resource.
Business Applications communities