[SalesForce] Dynamic SOQL Queries and Managed Namespaces

If I create a dynamic SOQL query (via strings, to be used with Database.query) in an unmanaged code environment, and then the code is converted to a managed environment, are namespace considerations taken into account? Or do I need to ensure I've prefixed my managed object names with the namespace of the managed package while assembling the dynamic SOQL query.

Best Answer

If you create dynamic SOQL queries and then later go to package the code in a managed package, you don't need to consider the prefix in your queries, the platform will magically know that the objects/fields are part of your package (assuming they were) and do the magic for you.

For example, if you had this SOQL in a class:

List<SObject> listOfThings = Database.query('Select MyField__c From Things__c');

And then eventually converted the package to a managed package with namespace prefix MyPKG you would not need to code it as:

List<SObject> listOfThings = Database.query('Select MyPKG__MyField__c From MyPKG__Things__c');

Related Solutions

Apex Dynamic SOQL – Convert Set to String for Dynamic SOQL IN Comparison

Believe it or not bind variables actually work in dynamic SOQL:

Map<Id,Account> accts = new Map<Id,Account>([select Id from Account]);
Set<Id> accountIds = accts.keySet();
String q = 'select id from Contact where AccountId in :accountIds';
List<Contact> cts = Database.query(q);

Note that you can't embed method calls (e.g. AccountId in :accts.keySet() would fail) when binding in this way.

This is a very, very good way of doing things as it offers a massive reduction in script statements, heap space, and even added security by automatically escaping input. I believe it also means that the bind data doesn't count against the 10k SOQL query character limit.

~~I can confirm there are a number of ISV apps that are dependent on this so there's no way salesforce could remove it in a future version without a massive outcry.~~ This method is actually salesforce endorsed!

Also, see this question if you're having trouble with more complex uses, in short: you can only use an in-scope variable, not an actual expression with these binds.

[SalesForce] CurrencyIsoCode – Auto included in query results, except for test cases

Wow that is strange and can confirm I have just tried it myself! Also agree would like to see that become the default! It is not great to have to resort to Dynamic SOQL just for this and loose the compile time checking and dependency enforcement it brings, especially when packaging solutions on the platform.

We have partly worked around this and the dynamic introduction of CurrencyIsoCode in this Selector Enterprise App pattern, while also leveraging Apex Describe literals to retain the compile time checking and dependency references.

In the meantime I would really like to know from Salesforce if this was an accident or if the lack of this in test is a bug that will someday be fixed!

Best Answer

Related Solutions

Apex Dynamic SOQL – Convert Set to String for Dynamic SOQL IN Comparison

[SalesForce] CurrencyIsoCode – Auto included in query results, except for test cases

Related Topic