1. Lessons learned from a Developer
Presenters:
Mark Carrington – Data8
Matt Beard – Data8

2. Mark Carrington Chief Technologist CRM 4 – Dynamics 365
Summit Nashville 2017
9/6/2018 7:40 PM
Mark Carrington
Chief Technologist
CRM 4 – Dynamics 365
© 2017 Dynamic Communities. All rights reserved.

3. Mark Carrington Matt Beard Senior Developer CRM 2011 – Dynamics 365
Summit Nashville 2017
9/6/2018 7:40 PM
Mark Carrington
Matt Beard
Senior Developer
CRM 2011 – Dynamics 365
Chief Technologist
CRM 4 – Dynamics 365
© 2017 Dynamic Communities. All rights reserved.

4. Matt Beard Senior Developer CRM 2011 – Dynamics 365
Summit Nashville 2017
9/6/2018 7:40 PM
Matt Beard
Senior Developer
CRM 2011 – Dynamics 365
© 2017 Dynamic Communities. All rights reserved.

5. What is this session? What is this session about?
Attempting to stop those regular mistakes
Reminder that you might not be doing it wrong
Sharing our headaches, to save yours
Good mix of C# & Javascript

6. What sort of lessons? AutoComplete Custom Attributes
Merging & EntityReference
WebAPI
Changing metadata

7. What next? We are developers We don’t like slides Let’s see some code…
github.com/Data8

8. AutoComplete

9. AutoComplete – What we learnt?
Lookup field required on the form
getValue() from the attr, not the control
onChange() triggered twice, once with typed value and once with resulting value
Only first field can be directly used

10. Custom Attributes

11. Attributes – What we learnt?
Just because you can, don’t
Custom attribute name prefixes are there for a reason, so use them

12. SDK Merging

13. SDK Merging – What we learnt?
Setting EntityReference through UpdateContent can cause unforeseen errors
Ensure “name” is null to be sure merge will complete

14. WebAPI

15. WebAPI – What we learnt?
Filtering using Customer attributes needs “_account” or “_contact” suffix
Queries all use collection logical name
Not always just adding ‘s’ either
Guids require { } to be removed
Expanding child collections can give old cached results

16. Changing Metadata

17. Changing Metadata – What we learnt?
Reducing attribute length won’t cause truncation
You can still access values that are too long
You cannot set that value to any other record
Customs actions cache heavily
Changing signatures can give false 204 or 400 results

18. Any Questions? Any other headaches to avoid?

19. Please fill in your feedback forms for this session!
Presenters:
Mark Carrington – Data8
Matt Beard – Data8