cic 2008-11-14T21:46:04Z I'm afrad that this Use Case has not been delivered. Dynamic SOQL does in theory give this, but it has been completely made usless by the security model. Namely. 1. A managed package cannot access extra fields that are added to the custom objects of that package. The security model forbids it. 2. That same managed package, whilst in the original developer org, cannot access any objects of fields at all. You have to write the code and hope it will work when installed. 3. A managed package cannot access extra fields add to any of the standard objects - even if the customer has given permission for the package to access that object. The only thing you can do with dynamic SOQL is to access (some of) the objects and fields that you know about at compile time. This "Idea" is now a request to relax those security rules so we can use the power of dynamic SOQL for our ISV apps. tmatthiesen 2008-10-14T09:10:24Z Changed status to <span class="status_tag">Delivered</span>. tmatthiesen 2008-08-18T15:53:51Z Changed status to <span class="status_tag">Ideas Under Consideration</span>. elinkbiz 2008-08-11T22:46:20Z The ability to dynamically generate and execute SOQL code in APEX. This feature would provide the following: - Allow dynamic creation of stored proceedure like strings and execute - The ability to start creating resource bundles of SOQL code that can be reused easier throughout the application - The ability to introspect objects and create custom SOQL code based on object descriptions - This is EXTREMELY useful for Partners & Developers writing APEX applications - It could support auto-boxing between SOQL Code implementation today and SOQL String based implementations Example code snipet: String statement = 'select id, name from Account where name=blah'; Account [] accountList = SOQLService.execute(statement); chuckgoss02202008 2008-08-06T09:05:04Z Please make this generally available without restriction, so we can deploy it in our managed package! Wilmer 2008-07-22T16:35:34Z Hi Scott, Well, now we're on Summer'08 and the truth is that unfortunately this feature has not been officially released because look what happened to us... 1) It was necessary to contact a support agent to turn it on in our Sandbox, 2) Finally, when we developed a new solution based on this new feature (which is very good in fact) we've been told ACTIVATION in production wasn't possible at this moment because there were some internal testing pending. So, we couldn't use it at all. Please, let us know when this could be possible. Thanks. din 2008-07-06T12:33:49Z Allow dynamic SOQL in Apex Code. This will enable executing business rules dynamically based on user selections. TehNrd 2008-05-20T19:50:40Z Yup, I totally lapsed on that one. Thanks for clarifying. Scott_Jorgensen 2008-05-19T23:03:40Z Changed status to <span class="status_tag">Ideas Under Consideration</span>. Scott_Jorgensen 2008-05-22T16:21:02Z TehNrd: This idea has made it to Developer Preview for Summer '08...so I think "Under Consideration" is more appropriate. Here are the details from the Release Notes: https://na1.salesforce.com/help/doc/en/salesforce_summer08_release_notes.pdf Dynamic Apex Dynamic Apex is composed of dynamic SOQL and SOSL queries, as well as dynamic DML. Dynamic SOQL and SOSL queries provide the ability to execute SOQL or SOSL as a string at runtime, while dynamic DML provides the ability to create a record dynamically and then insert it into the database using DML. Using dynamic SOQL, SOSL, and DML, an application can be tailored precisely to the organization as well as the user's permissions. This can be useful for applications that are installed from the AppExchange. For more information, see: Dynamic SOQL Dynamic SOSL Dynamic DML TehNrd 2008-05-14T12:47:53Z According to the summer08 release notes this should be marked as 'Coming Summer 08' xn 2008-04-25T16:20:58Z In short, you should be able to use a string as a soql query. Siddharth 2008-04-21T03:52:25Z I agree with megar, APEX should allow to build a dynamic query using the if else blocks. BobMorrell 2008-02-11T07:45:48Z Agree with billa. This is a base line feature if this is to be considered a viable development environment. megar@apprivo.com 2008-01-22T18:30:50Z There is also a need for dynamic SOQL when field names are known. This is important for bulking up queries. There isn't any way to do this for queries where the IN operator can't be used. billa 2007-12-06T17:17:44Z APEX is near worthless until this is done. misterk17811122007 2007-12-06T17:17:43Z Agree. This would be a very powerful feature. jholtz17 2007-12-06T17:17:41Z I second that! Wilmer 2007-12-06T17:17:41Z This could be very useful to developers to design and develop really customizable customer app and extend power of Salesforce. Rusty12 2007-12-06T17:17:41Z i'm sure there are a number of technical challenges to make this happen, but if implemented it would increase the power/potential of what type of Apps can be built w/ Apex Code by 10 fold. Scott_Jorgensen 2007-12-06T17:17:23Z Aha!! I stand corrected. You've got a great suggestion: add the ability to have queries be dynamic in Apex just like the API does using the Partner WSDL. cic 2007-12-06T17:17:21Z I am refering to Apex Code SOQL - not the API. Scott_Jorgensen 2007-12-06T17:17:13Z You should be using the "Partner WSDL" if you're an ISV. You are correct that the "Enterprise WSDL" is specific to a particular Organization, but the "Partner WSDL" is identical across all Organizations. You can learn more about the Partner WSDL here: http://www.salesforce.com/us/developer/docs/api/index_CSH.htm#sforce_api_quickstart_steps.htm