# Missing consistency in error and web request mapping

**URL:** https://community.appfarm.io/t/missing-consistency-in-error-and-web-request-mapping/874
**Category:** Feature requests
**Tags:** app-data, service
**Created:** [November 24, 2023, 11:30am UTC](https://community.appfarm.io/t/missing-consistency-in-error-and-web-request-mapping/874 "2023-11-24T11:30:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Sondre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/sondre/32/105_2.png) [@Sondre](https://community.appfarm.io/u/Sondre)
#### Post date: [November 24, 2023, 11:30am UTC](https://community.appfarm.io/t/missing-consistency-in-error-and-web-request-mapping/874/1 "2023-11-24T11:30:32Z")

</div>

Hi,

When catch error mapping to App Data in an app, only the attributes mapped to is affected.  
When error mapping to a runtime Object in an app the entire object is replaced.  
When web request response mapping to Service Variables all service variables is reset.

It would be very nice if this type of mapping had consistent behavior. And in my opinion it should have the default behavior of updating the runtime object or updating the service variables like app variables inn apps on error mapping.

It is of course very possible to work around but it has created some confusion and if the “replace” behavior is kept it creates more “clutter” in an already long list of app variables for instance.

Edit: Maybe app/service variables by default stays and to runtime objects you have a optional toggel of replace object like in “read to” 🙂

---

<div class="post-metadata">

### Author: ![karlh](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/karlh/32/2567_2.png) [@karlh](https://community.appfarm.io/u/karlh)
#### Post date: [November 27, 2023, 11:23am UTC](https://community.appfarm.io/t/missing-consistency-in-error-and-web-request-mapping/874/2 "2023-11-27T11:23:06Z")

</div>

Hi there,  
Thank you for your feedback related to improved consistency when mapping data to various datasource-types.  
I have submitted this as a feature request to our product-team.
