# \[DONE\] Append Rich Text fields in Update action in automations **URL:** \ **Category:** Ideas & Features\ **Tags:** automations\ **Created:** [September 26, 2024, 4:55pm UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724 "2024-09-26T16:55:43Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [September 26, 2024, 4:55pm UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/1 "2024-09-26T16:55:43Z")
> [@Sep 26, 2024 / blowfish Share Database, Quick filters in Views, Slack Bot improvements, and more](https://community.fibery.io/t/sep-26-2024-share-database-quick-filters-in-views-slack-bot-improvements-and-more/6719/1): > > All Rich Text fields are available in Create/Update actions, and you can fill them via Formula, AI call or Markdown template. This is so awesome! We use a lot of templates for description fields. Only problem that occurs now is that we can’t use a formula when we want to append to a rich text field. It’s only possible with the ‘append/prepend’ function. But if you use that, all call out blocks and other cool stuff will be gone. That’s why we currently use a script so that we can have the html content ```auto const fibery = context.getService('fibery'); for (const destination of args.currentEntities) { const source = await fibery.getEntityById('DB automatiseringen en templates/Template - Omschrijving', destination['Template voor omschrijving']['Id'], ['Omschrijving']); const sourceContent = await fibery.getDocumentContent(source['Omschrijving']['Secret'], 'html'); await fibery.appendDocumentContent(destination['Omschrijving']['Secret'], sourceContent, 'html'); } ``` Would be great if we don’t need this script anymore. (If you use the update function + a formule, you will get an exact copy of the rich text field. But it will always overwrite the description field, never append) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 26, 2024, 5:40pm UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/2 "2024-09-26T17:40:31Z")
> [@YvetteLans](#): > > Would be great if we don’t need this script anymore. We will think. Technically it is easy to do, but we should invent some UI ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [September 26, 2024, 5:53pm UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/3 "2024-09-26T17:53:54Z")
> [@mdubakov](#): > > but we should invent some UI An option without changing UI - When the action is one of these ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/cb0653daaa5b0f3c066bb2b5bdc7174941153ad2.png) - And a rich text field is mentioned via markdown (i.e. [Step 1].Template.Description) - Then always put the HTML version of the entity in the description field (instead of the markdown version) But I don’t know if that’s technically easy to do and if there are any cons. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 27, 2024, 10:03am UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/4 "2024-09-27T10:03:45Z")
We will add Formula setting for these actions in the next release, so it will work fine for your case ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [September 27, 2024, 10:21am UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/5 "2024-09-27T10:21:50Z")
Awesome, thank you so much! 🤩 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 3, 2024, 11:57am UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/6 "2024-10-03T11:57:17Z")
Implemented in latest release > [@October 3, 2024 / maple\_leaf Quick filters on relation and embedded views, Clean email body, Automations Script AI Assistant, and more](https://community.fibery.io/t/october-3-2024-quick-filters-on-relation-and-embedded-views-clean-email-body-automations-script-ai-assistant-and-more/7492): > > In today’s release we added several improvements to recently released features and made a first step to AI Automations assistant. This is the recent feedback we’ve got from one our customer and it generated a lot of dopamine for our team, just want to share it with you as well. I’m deeply impressed by the technical design of Fibery — you guys seem to make excellent trade-offs and design decisions, preferring to add more powerful & simple higher-level abstractions, rather than special-case feat… ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 3, 2024, 12:05pm UTC](https://community.fibery.io/t/done-append-rich-text-fields-in-update-action-in-automations/6724/7 "2024-10-03T12:05:08Z")