forked from django-salesforce/django-salesforce
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Phil Christensen edited this page Jul 27, 2016
·
12 revisions
- Empty strings - How to exclude empty strings in queries etc.
- Error messages - How to understand some strange error messages
- Experimental Features - dynamic authentization, multiple SF databases with Admin
- Foreign Key Support - queries based on fields of related tables, Many2Many relationships
- Introspection and Special Attributes of Fields - How to understand the database model exported by inspectdb and how to exactly describe Salesforce by the the model.
- SSL TLS settings and Saleforce.com, but a better solution is to upgrade SSL/TLS system libraries and Python.
- Tuning REQUESTS_MAX_RETRIES - A variable used in edge-cases that is difficult to describe, see this issue for more info.
- Excluding Empty Strings - An issue that results from the leaky abstraction between Salesforce and an RDBMS.
- Converting Leads - Converting leads is not directly supported by the Salesforce REST interface, but an included helper function can use beatbox and the SOAP interface.
In both Django and Salesforce double underscores are significant, so to make custom fields work in Django, be sure to specify the db_column argument in the model field definition, i.e.
Last_Login = models.DateTimeField(db_column='Last_Login__c',max_length=40)
The tests can be slow with Django 1.7 and 1.8, if the default database has many migrations and some are applied and complex models for salesforce database are used, e.g. hundreds kB exported by inspectdb without pruning (--table-filter=...). This is fixed by Django 1.9 or many workarounds are described on the Internet for old Django.