# Table Property Mapping

DevFeed: [Table Property Mapping](<https://devfeed.tech/articles/table-property-mapping-19543.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/table-property-mapping/>)

Author: Shai Almog

Published: 2018-08-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [API](<https://devfeed.tech/topics/api.md>), [ui](<https://devfeed.tech/topics/ui.md>), [data](<https://devfeed.tech/topics/data.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [code](<https://devfeed.tech/tags/code.md>), [data](<https://devfeed.tech/tags/data.md>), [json](<https://devfeed.tech/tags/json.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [property](<https://devfeed.tech/tags/property.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [ui](<https://devfeed.tech/tags/ui.md>)

## AI overview

A Codename One update adds an API for binding lists of property objects to tables, enabling table creation without manually writing binding code. The article demonstrates persisting object lists as JSON, including standardized date representations, and building editable tables with picker controls.

## Source excerpt

If you aren't using properties with Codename One, you probably should. Here's a post I wrote a while back covering them, it should give you a lot of reasons for this. We are slowly integrating them into API's such as Rest and as a result the code is simpler. A huge bonus is the type safety and flexibility that comes with this API. Up until now binding in properties was mostly limited to "simple" classes such as TextField. Complex structures such as Table weren't supported. This is no longer the case.