# configureCell Return Attributes Syntax

**URL:** <https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [February 21, 2022, 4:24pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375 "2022-02-21T16:24:18Z")\
**Posts on this page:** 6\
**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:** [February 21, 2022, 4:24pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375/1 "2022-02-21T16:24:18Z")

</div>

I have a configureCell script set up to change the font of specific cells in a power table. Is there a list of attributes that can be returned in the dictionary and their syntax?

“font” : “Lucida Console, Plain, 12” works  
but  
“Foreground Color” : “213,213,213” does not work

Would be nice to know exactly which keys and value types it’s looking for.

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 21, 2022, 5:06pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375/2 "2022-02-21T17:06:16Z")

</div>

From the manual:

Provides a chance to configure the contents of each cell. Returns a dictionary of name-value pairs with the desired attributes. Available attributes (and their Java types) include: **‘background’** (color), **‘border’** (border), **‘font’** (font), **‘foreground’** (color), **‘horizontalAlignment’** (int), **‘iconPath’** (string), **‘text’** (string), **‘toolTipText’** (string), **‘verticalAlignment’** (int).

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [February 21, 2022, 5:13pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375/3 "2022-02-21T17:13:21Z")

</div>

Oops, I hit send before I was ready. 🙄

I think you can define it close to the way you had, but you may have to import [java.awt.Color](https://docs.oracle.com/javase/7/docs/api/java/awt/Color.html) to do it.

That said, here’s a couple of easier ones:  
A hex value `{'foreground': 'D5D5D5'}`  
A named color `{'foreground': 'blue'}`

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 22, 2022, 4:11pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375/4 "2022-02-22T16:11:59Z")

</div>

`system.gui.color(213, 213, 213)` would also work.

---

<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:** [March 9, 2022, 7:48pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375/5 "2022-03-09T19:48:52Z")

</div>

Any way to return a template to show in the cell?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 9, 2022, 7:54pm UTC](https://forum.inductiveautomation.com/t/configurecell-return-attributes-syntax/56375/6 "2022-03-09T19:54:03Z")

</div>

Not trivially. Technically you could embed a live component, but it would take some serious finagling.