Lessons learned from a Developer explore engage elevate

  • Slides: 19
Download presentation
Lessons learned from a Developer explore engage elevate Presenters: Mark Carrington – Data 8

Lessons learned from a Developer explore engage elevate Presenters: Mark Carrington – Data 8 Matt Beard – Data 8

What is this session? What is this session about? Attempting to stop those regular

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 explore engage elevate

What sort of lessons? Auto. Complete Custom Attributes Merging & Entity. Reference Web. API

What sort of lessons? Auto. Complete Custom Attributes Merging & Entity. Reference Web. API Changing metadata explore engage elevate

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

What next? We are developers We don’t like slides Let’s see some code… github. com/Data 8 explore engage elevate

Auto. Complete explore engage elevate

Auto. Complete explore engage elevate

Auto. Complete – What we learnt? Lookup field required on the form get. Value()

Auto. Complete – What we learnt? Lookup field required on the form get. Value() from the attr, not the control on. Change() triggered twice, once with typed value and once with resulting value Only first field can be directly used explore engage elevate

Custom Attributes explore engage elevate

Custom Attributes explore engage elevate

Attributes – What we learnt? Just because you can, don’t Custom attribute name prefixes

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

SDK Merging explore engage elevate

SDK Merging explore engage elevate

SDK Merging – What we learnt? Setting Entity. Reference through Update. Content can cause

SDK Merging – What we learnt? Setting Entity. Reference through Update. Content can cause unforeseen errors Ensure “name” is null to be sure merge will complete explore engage elevate

Web. API explore engage elevate

Web. API explore engage elevate

Web. API – What we learnt? Filtering using Customer attributes needs “_account” or “_contact”

Web. API – 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 explore engage elevate

Changing Metadata explore engage elevate

Changing Metadata explore engage elevate

Changing Metadata – What we learnt? Reducing attribute length won’t cause truncation You can

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 explore engage elevate

explore engage elevate Any Questions? Any other headaches to avoid?

explore engage elevate Any Questions? Any other headaches to avoid?

Please fill in your feedback forms for this session! explore engage elevate Presenters: Mark

Please fill in your feedback forms for this session! explore engage elevate Presenters: Mark Carrington – Data 8 Matt Beard – Data 8