Our Blog

This article demonstrates the implementation of "Dable" (pronounced 'dabble')  plugin in Visualforce page for pagination, sorting and searching on the client side.

Now that the backend controllers and Apex code blocks are in place (with appropriate test classes, hopefully!), the VF page can be put together simply as an apex:form with a category filter, a table of recommendations data and a section for page navigation.
The save action on the form can be mapped to the extension to save the appropriate recommendations records by querying the changed recommendations cache.

Continuing on from Part 1, where we defined a data structure to hold our recommendation junction objects, this part will focus on the state management required for the UI.  

The number of clicks required to create a related list record against a master is tedious. It gets more complex if we require to pick and choose a number of the other parent records to create records against. somewhat like the opportunity product list where we create Opp- Products against the opportunity but by choosing the product to peg it against. 

Another example of this is the "Fund Recommendations List" on Accounts or "Selected Funds" on Opportunity etc from the Arxxus Solution for Fund Managers.

Let us discuss a technique to model this scalably using VF and Apex so that we are able to filter and paginate through tons of records to create required related records easily directly off the parent record. 

In today’s world everyone needs ease of data access, by reducing the number of clicks for the users, you can increase the user adoption of Salesforce by heaps.