Dynamic Custom Fields
Most SaaS products let their customers create custom fields.
Each customer chooses different names and uses a different subset of fields.
Sisense does not support this natively. A typical OEM data model exposes generic placeholders such as: f1, f2, f3, f4, f5.
Your application knows what these mean for each customer. Sisense doesn’t, so it shows all placeholders to everyone.
Result:
- Users see irrelevant fields
- Customers complain about empty fields
- You maintain Metadata rules manually
- Some OEMs create one cube per customer
- Onboarding becomes slow and messy
The Dynamic Custom Fields plugin solves all of this.

How the plugin works (real example)
Let’s say your shared schema has 5 generic fields: f1, f2, f3, f4, f5.
Your application stores the meaning of these fields in a mapping table.
Customer A:
- f1 → Product Tier
- f2 → Contract Owner
- f3 → Priority Level
- f4 → (not used)
- f5 → Renewal Score
Customer B:
- f1 → Region Category
- f2 → Account Owner
- f3 → (not used)
- f4 → Account Segment
- f5 → Churn Rating
This means:
- Both customers share f1 and f2 but name them differently
- Customer A uses f3 and f5
- Customer B uses f4 and f5
- Sisense normally shows all 5 placeholders
- The plugin filters and renames fields per user
Customer A sees:
Product Tier
Contract Owner
Priority Level
Renewal Score
Customer B sees:
Region Category
Account Owner
Account Segment
Churn Rating
Without the plugin:
f1, f2, f3, f4, f5 appear for everyone.
What problems this solves:
1. Users stop seeing irrelevant fields
2. You no longer need the Metadata plugin to rename fields
3. You keep a single cube for all customers
4. Your UI becomes accurate everywhere
5. You avoid major OEM BI scaling issues
Where the plugin works inside Sisense
- Dashboard Filter
- Widget Filter
- Widget data panel
- Formula Editor
Additional capabilities
- Auto-detection of new custom fields
When customers add fields in your app, the mapping updates and the plugin automatically:- Adds the new field to filters
- Shows it in formulas
- Shows it in widget panels
- Hides unused placeholders
- Integration with Paldi plugins
- Expandable Pivot – dynamic fields as pivot dimensions.
- Advanced Table – sortable, filterable, exportable dynamic fields.
- Dim Switcher – dynamic fields as switchable dimensions.
Who should use this plugin
This plugin is ideal for Sisense implementations where:
- Customers define their own custom fields
- A single shared schema needs to support many tenants
- Field names differ from customer to customer
- Only relevant fields should appear in Sisense dialogs
- You want to avoid cube duplication or per-customer metadata work
If your product relies on dynamic custom fields, this plugin is the cleanest way to make Sisense reflect your application’s logic accurately.

Enhance your Sisense Experience With our Top Rated Reporting Suite
see faster adoption, richer insights, and greater ROI.





"With the help of Paldi Plugins, you can just click and it’s there.
We were able to leverage Sisense to create a better user experience from a designer and user perspective."




