# Export all component text used in Ignition

**URL:** <https://forum.inductiveautomation.com/t/export-all-component-text-used-in-ignition/53668>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [December 2, 2021, 1:36pm UTC](https://forum.inductiveautomation.com/t/export-all-component-text-used-in-ignition/53668 "2021-12-02T13:36:31Z")\
**Posts on this page:** 1\
**Showing post:** 19

<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:** [February 28, 2022, 3:21pm UTC](https://forum.inductiveautomation.com/t/export-all-component-text-used-in-ignition/53668/19 "2022-02-28T15:21:27Z")

</div>

> [@victordcq](#):
>
> try this: `component.getPropertyValue('text1')`

Pssst! Just install Simulation Aids and the shortcuts will always work (`component.text1`) even for custom properties, and no matter what method you used to get the component reference. See this discussion:

> [@Transaction groups triggered expression item updating when trigger is false](https://forum.inductiveautomation.com/t/transaction-groups-triggered-expression-item-updating-when-trigger-is-false/17196/14):
>
> Ok, so I’ve been down the rabbit hole and found Ignition’s (undocumented) PyComponentWrapper. I haven’t deciphered it enough to be sure, but it seems to be invoked only for particular situations, based on the string constants in the class file (like “getComponent” and “getComponents”). To play with this, I constructed a conversion adapter like so: public class PyComponentAdapter implements PyObjectAdapter { public PyComponentAdapter() {} @Override public boolean canAdapt(Object jObj) { …

---

_[View the full topic](https://forum.inductiveautomation.com/t/export-all-component-text-used-in-ignition/53668)._