# Setting a Name for Encoded Text in a Container

**URL:** <https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593>\
**Category:** Questions\
**Created:** [January 11, 2021, 7:31am UTC](https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593 "2021-01-11T07:31:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [January 11, 2021, 7:31am UTC](https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593/1 "2021-01-11T07:31:55Z")

</div>

I'm using the TextEncode( ) function on text and then placing it into a container field. When I do this the container displays "utf-8.txt", which is the format I used and ".txt". Is there anything that we can do during the TextEncode( ) or some other step that will allow us to set a more specific name?

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [January 11, 2021, 8:33am UTC](https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593/2 "2021-01-11T08:33:45Z")

</div>

Hi @Malcolm ,

_Base64Decode_ allows for specifying a file name, but it's difficult for me to feel good about suggesting to Base64-encode the data, only to then reverse the encoding, even if it does yield a nicer display. But maybe it's food for thought that will inspire some other, better, approach.

 ![filename](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/5/51a02f983a03ef41b427538fbac28909081b526d.png)

---

<div class="post-metadata">

**Author:** ![Torsten](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/torsten/32/1574_2.png) [@Torsten](https://the.fmsoup.org/u/Torsten)\
**Post date:** [January 11, 2021, 4:49pm UTC](https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593/3 "2021-01-11T16:49:09Z")

</div>

As separate text field for holding a name or description could be a solution.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [January 11, 2021, 6:21pm UTC](https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593/4 "2021-01-11T18:21:14Z")

</div>

Interesting that the file name hangs around after the Base64Decode. In the current environment I'm not handling large files. Even so, I think @Torsten is making a sensible suggestion. I can pass store a file name easily enough. I don't want to have someone call when the text dumps have grown to a large size and they are wondering why the transfer has slowed to a crawl.

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [January 11, 2021, 6:30pm UTC](https://the.fmsoup.org/t/setting-a-name-for-encoded-text-in-a-container/1593/5 "2021-01-11T18:30:56Z")

</div>

Completely agreed. I like what @Torsten proposes.