Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Pentaho CTools

You're reading from   Learning Pentaho CTools Acquire finesse with CTools features and build rich and custom analytics solutions using Pentaho

Arrow left icon
Product type Paperback
Published in May 2016
Publisher Packt
ISBN-13 9781785283420
Length 388 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Miguel Gaspar Miguel Gaspar
Author Profile Icon Miguel Gaspar
Miguel Gaspar
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Getting Started with CTools FREE CHAPTER 2. Acquiring Data with CDA 3. Building the Dashboard Using CDF 4. Leverage the Process with CDE 5. Applying Filters to the Dashboard 6. Tables, Templates, Exports, and Text Components 7. Advanced Concepts Using CDF and CDE 8. Visualizations Using CCC 9. Pentaho App Builder 10. Embed, Deploy, and Debug Index

References to components, parameters, and layout elements


First, I want to start by covering one important concept in CDF, and don't forget that concepts in CDF also extend to CDE. If you open the developer tools in your browser and start inspecting some CDE dashboard code, you will see that the names of the components are always prepended with render_ with the name of the components that we set when editing the dashboard. This way, when you want to refer to a component using its name, you should use the complete name of the component such as:

this.dashboard.getComponentByName('${c:myComponentName}');

This would be the same as:

this.dashboard.getComponentByName('render_myComponentName');

When you use this code line inside a dashboard, where it is not valid for code in external files, you can refer to the component as ${c:myComponentName}. This is possible because, when using this syntax, it will be translated and replaced by the full name of the component, so you don't need to worry about the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime