Oh, I see, don't keep it to yourself next time
Then, a DynamicList is your option.
OR if there are many cases in which you want a slim version of this specific entity, and you want to fetch it in a read-write way without the extra fields (eg. BLOB fields)
You may use the Designer to map another entity into the same table, but this time you remove the unwanted fields.
This results in having 2 entities to deal with the same table (eg. CustomerEntity & CustomerSlimEntity )