1. Dynamic Visualforce& Fieldsets Tim Youngblood Cofounder & CTO

3. Goals

4. Why Dynamic VF?

5. Who needs Dynamic VF?

6. Dynamic aspects of the Force.com platform

7. Dynamic Visualforce

8. Fieldsets

10. Based in Atlanta and San Francisco

11. Focus:

12. Force.com development: both for- and non-profit clients

13. Data integration:

14. IBM CastIron™

15. Dell Boomi™ Partner

16. AppExchange product development:

17. Constant Contact InfoTransfer

19. What is involved roughly to implement

21. Maintenance is the true cost of software

22. Empower the System Admin is a good philosophy

24. Do you have projects that have a large number of fields involved? >100

26. SObject: superclass

27. Metadata: Schema

29. Expression: evals to a string indicating a field or child object

31. Object1__c[‘Object2__c. Field1__c’]

32. Object1__c[‘Object2’][‘Field1__c’]

33. Object1__c.Relationship__r[Field1__c]

34. Object1__c[Relationship__r. Field1__c]

36. Example #2 Fairly simple example 2: same across metadata driven field names. <apex:repeat value="{!accountFields}" var="field"> <apex:inputField value="{!Account[field]}" /> </apex:repeat> public List<String> getAcctFields() { Map<String, Schema.SObjectField> fieldmap = Schema.SObjectType.Account.fields.getMap(); List<String> fieldlist = new List<String>(); for(String fieldname: fieldmap.keyset()) { fieldlist.add(fieldname); } }

39. Allows configuration of available fields for DVF driven pages.

40. Are not accessible via Apex Code, as far as I can tell, which is a bit disappointing.

41. Is there database access to fieldsets? No.

44. Copious number of fields that change regularly

45. Repetitive GUI elements

46. Dynamic section on a standard page is a good use case

47. What is involved roughly to implement

48. reference[expression] inside an <apex:repeat>

50. Fieldsets order can be controlled by config.

51. Need access to Fieldsets from Apex!