Join us in this Technical Deep Dive into some key SDK functionality introduced with the 2015 Spring Update release! This session is for CRM Developers & Architects.
2. Agenda
• SDK Enhancements
• New form script capabilities and Deprecated methods
• Calculated and Rollup fields
• Tracing Logs
• Alternate Keys
•Deprecated
•Deprecated
3. SDK Enhancements
• Alternate Keys
• Calculated and Rollup fields
• Upsert for updating CRM with external data
• Plugin Trace Logging
• Entity Change Tracking
• Multiple message execution
• Optimistic Concurrency
• Custom actions in workflows or dialogs
• Support for additional “older than” clauses for date and time fields in FetchXML and
QueryExpression
4. New form script capabilities
• Enhanced capabilities for sub-grid controls in forms
• More options to open forms
• Control.getShowTime method for Date controls
• Identify the type of device being used
5. Limitation for subgrid control in CRM 2015
• Only method available for a subgrid control is refresh
• Can not be called in onLoad Event
7. More options to open forms
• openQuickCreate
Syntax :-
Xrm.Utility.openQuickCreate(entityLogicalName,createFromEntity,parameters).then(successCallback, errorCallback);
• openEntityForm
Syntax :-
Xrm.Utility.openEntityForm(name,id,parameters,windowOptions)
9. Identify the type of device being used
Syntax: - var intDeviceType = context.client.getFormFactor();
Return Type: Number
Value Device
0 Unknown
1 Desktop
2 Tablet
3 Phone
13. Calculated Fields
• The calculated fields comprise of calculations that use the fields from the current entity or related parent entities.
• The expression support is available on the current entity and the related parent entity fields in the Condition sections and
the Action sections.
• A rich conditional support provides branching and multiple conditions. The logical operations
include AND & OR operators.
• The visual editing capabilities include modern user interface and intellisense in the ACTION section.
• A seamless integration of the calculated fields with the forms, views, charts, and reports is available in real time.
New In CRM 2015 Update 1
• will now be able to calculate the difference between two date fields in minutes, hours, days, weeks, months, or years.
• The Now() Function
15. Limitation of Calculated Fields
o maximum of 10 unique calculated fields
o calculated field values will not updated in the CRM Outlook Offline mode.
o A maximum number of chained calculated fields is 5
o Sorting is disabled.
o You can’t trigger workflows or plugins on calculated fields
o You can’t change an existing simple field to a calculated field.
o Duplicate detection rules are not triggered on calculated field.
o A rollup can't reference a calculated field that uses another calculated field,
16. Rollup fields
o Visual editing is easy
o Seamless integration with the user interface
o Rollup fields are solution components
o Rollup fields and the calculated fields are complementary to each other
New In CRM 2015 Update 1
• Full filter support for aggregation
• Wide selection of aggregate functions
• Support using Rollup fields with activities
18. Limitation of Rollup fields
• You can define a maximum of 100 rollup fields for the organization and up
to 10 rollup fields per entity.
• A workflow can’t be triggered by the rollup field updates.
• A workflow wait condition cannot use a rollup field.
• A rollup over the rollup field is not supported.
• A rollup can't reference a calculated field that uses another calculated field,
even if all the fields of the other calculated field are on the current entity.
19. Limitation of Rollup fields
• The rollup can only apply filters to the source entity or related entities,
simple fields or non-complex calculated fields.
• A rollup can be done only over related entities with the 1:N relationship. A
rollup can’t be done over the N:N relationships.
• The business rules, workflows or calculated fields always use the last
calculated value of the rollup field.
20. Tracing Logs
• Ability to log tracing information to entity
• User does not have to create a separate entity to track the Error.
22. Limitation of Tracing Logs
• Trace logging takes up organization storage space especially when many
traces and exceptions are generated
23. Alternate Keys
• Reducing roundtrips
• Increasing overall throughput
• Simplifying programming
• Avoid users to write plugin to identify the duplicate records
• Faster lookup of the records
25. Limitation of Alternate Keys
• Can be created only on Decimal Number, Whole Number & Single line text
• Can define only up to five different keys for an entity
26. 2015 CloudFronts Technologies LLP, All Rights Reserved. 26
Contact us:
www.cloudfronts.com
info@cloudfronts.com
https://twitter.com/cloudfronts
https://www.youtube.com/cloudfronts
https://www.linkedin.com/pub/anil-shah/4/52b/a62
27. Upcoming Webinars:
• October 21st – Sales Productivity in CRM Online & CRM 2016 Features
Review
• October 27th – Using the Service Module in CRM
• October 28th – ClickDimensions Marketing Automation & Analytics Deep
Dive
• October 29th – Power BI Features Deep Dive