Best Practice for UI Builder

[Prithvi Ramesh1]

What should be the approach to show multiple reports to the customer in UI Builder? Should we use data visualization components with filters applied to relevant tables, or use indicator sources and schedule a daily job so the data doesn't load every time UI Builder is opened?

[M Iftikhar]

Hi Prithvi,

Great question! The best approach depends on your use case, but here are the guidelines:

Option 1: Data Visualization (Real-Time)

• When: Use if you need live/near real-time data and reports are optimized.

• How: Create reports via Report Builder and embed them in UI Builder (Report/Dashboard components). Apply filters as needed.

• Pros: Always current, no extra jobs.

• Cons: Can slow down if queries are heavy.

Option 2: Indicator Sources (Scheduled Jobs)

• When: Use if data can be snapshot-based (e.g., daily) or queries are heavy.

• How: Schedule indicator sources to precompute data, then display via charts/metrics in UI Builder.

• Pros: Faster load, less DB impact.

• Cons: Not real-time.

Recommendation:

• For interactive/live dashboards → use Data Visualization.

• For performance-sensitive or KPI snapshots → use Indicator Sources.

• In many cases, a hybrid approach (real-time for critical metrics + precomputed for heavy data) works best.

Hope this helps!

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.