# Component Extension Function Calls

**URL:** <https://forum.inductiveautomation.com/t/component-extension-function-calls/80662>\
**Category:** Ignition\
**Tags:** ignition81, scripting, vision\
**Created:** [October 18, 2023, 7:50pm UTC](https://forum.inductiveautomation.com/t/component-extension-function-calls/80662 "2023-10-18T19:50:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [October 18, 2023, 7:50pm UTC](https://forum.inductiveautomation.com/t/component-extension-function-calls/80662/1 "2023-10-18T19:50:42Z")

</div>

How do we know when extension functions are called? Some are fairly apparent, others not so much.

For instance, when does `EasyChart.configureChart()` run? When the chart first opens?

---

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [October 20, 2023, 6:46pm UTC](https://forum.inductiveautomation.com/t/component-extension-function-calls/80662/2 "2023-10-20T18:46:24Z")

</div>

Does anyone have some insights on this?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 20, 2023, 9:02pm UTC](https://forum.inductiveautomation.com/t/component-extension-function-calls/80662/3 "2023-10-20T21:02:38Z")

</div>

How often they run is an implementation detail. Fairly often for the EasyChart, not so much for the Classic chart.

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [October 21, 2023, 3:46am UTC](https://forum.inductiveautomation.com/t/component-extension-function-calls/80662/4 "2023-10-21T03:46:00Z")

</div>

> [@amarks](#):
>
> How do we know when extension functions are called?

For extension functions like `configureChart`, you could simply put a temporary `print 'I was called'` in the script somewhere, and watch the console as you interact with the component to get a feel for what triggers it.

However, there are a few extension functions like the power table's `configureCell` or the alarm status table's `filterAlarm` where print statements would be inadvisable due to the quantity of times that the extension function is called.

That said, even if an experimental print statement occasionally causes you to loose 30 minutes wrestling control of the designer from a overloaded gui, at least you'll have the information you are looking for.