Due to the fact that Salesforce record type IDs can vary between instances, it’s an important consideration to understand the effect of this on your design, development effort, and the potential failures once the app moves to production. As always with MobileCaddy, our aim is to remove this consideration to allow for more rapid and robust mobile apps.
Salesforce record types
For nearly every object in Salesforce (both standard and custom), you can create multiple record types of the same object. This allows separation of ‘types’ of records. For example, if we had a custom object for ‘assets’ (so Asset__c) we may want to store types of these assets that have shared, similar, and distinctively different attributes.
There’s an excellent video by CertifiedOnDemand which explains the concepts regarding why you would want to use record types, which I’ll refer to here, as our purpose is to look at the implications for our particular use case (here are some Salesforce tips and tricks on record types as well).