Skip to main content

Guide for Universal Table CMP users

About Us
Published by admin
27 January 2017
71

Universal table is a component for Salesforce.com, which allows creating a multi-function table with many useful features easily.

UniversalTableCMP consists of four parts: a component itself (UniversalTableCMP.component), its controller (UniversalTableController.cls), class to store records (NewRow.cls) and test class (TestUniversalTable.cls). The component creates the most versatile table that can be edited. It can work with 50000 rows.

To get started, four things need to be sent into the component with help of attributes:

  1. 'ListSize' – list of possible numbers of rows displayed per page. The first element will be applied. This attribute is not required. If a user does not send it into the component, the standard list will be applied.
  2. 'WhereCondition' – additional conditions for queries that will be placed after WHERE.
  3. 'ObjectsName' – a name of the SObject from which information for the table will be extracted.
  4. 'AllFields' - a special query that retrieves all the fields from the FieldSet. For example: SObjectType.ExOb__c.FieldSets.TotalFS.getFields(), where ExOb__c – SObject’s name, and TotalFS – name of this SObject’s FieldSet. The request may be triggered by the method of the controller.

It should look like this:

look

look

It is all that is necessary for the proper operation of the component.

The completed table looks like this.

guide

To move from page to page you should use image-links and links 'Next' and 'Previous'. If you are on the first or on the last page, then the appropriate link will be disable and you cannot press it.

On the right the current page number is displayed.

On the left user can set a number of rows displayed per one page. If you hover the cursor over the selectList, the information about displayed lines will pop up (the first and last row numbers, the total number of rows).

Next is the link 'optimum adjustment', pressing which you'll have a more accurate adjustment of each column width based on each record length.

guide-for-universal-table

If a user needs to sort the table by one of the columns, he should click on its title or arrow of this column. The arrow shows the order (ascending or descending) in which the table is sorted.

If you want to make a new record in the table, you need to press 'New'. This will open a popup of a standard page. After it closed your table will be reloaded automatically and a notification will appear. 'Edit' link works the same way.

If you want to delete a record from the table, press 'Del' link. After the operation, a notification will appear and your table will be reloaded automatically.

The component has a test coverage:

  1. UniversalTableControllerS – 100%.
  2. NewRow – 100%.

image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026