Hynek Cernoch

Short answer: ``` python noP_opportunities = opportunities.filter( pk__not_in=OpportunityLineItem.objects.filter(product2_id='any_id').values("opportunity_id") ) ``` --- Salesforce really doesn't support SOQL like `... WHERE NOT (Id IN (SELECT ...))` and the query must be `......

I will also raise an error preventive where SF returns invalid results, because an invalid result is worse than an exception.

We can wait with the new release 4.0.1 a few days until a test for this issue 302 is added and maybe something small related could need to be fixed.

You are right that an editable name field is a required field in forms, even that a null value can be passed by Salesforce REST API calls. In that case...

OK. If I fix it, can you please prepare some simple test data for it? That is to write simple models and data that allow me to create a `ContentDocumentLink`...

@gredondogc You wrote that you can write test data soon. I prepared a fixed code and I want to test it on the data. The fix could be included a...

You can add a custom manager to the model `ContentDocumentLink` that will call a method `.sf(minimal_aliases=True)` Then the right compiler can be used automatically for that model. The operator 'in'...

A good message is that a non-intuitive arrangement with `.sf(minimal_aliases=True)` will be not necessary soon because this bug is restricted only to the following well known five objects. ['ContentDocumentLink', 'ContentFolderItem',...

Yes, but it is currently an expected feature of Salesforce that can be circumvented in several possible ways by you. A simple information about it should be added to README....

(... continue) The model created by inspectdb should work easily. That's a right requirement. How we can achieve it: 1) Automatically refresh new values of fields with DefaultedOnCreate 2) Replace...