# The objectMapping option appears to be missing

**URL:** <https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088>\
**Category:** Help me!\
**Created:** [March 13, 2021, 3:56pm UTC](https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088 "2021-03-13T15:56:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jack\_Roberts](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/jack_roberts/32/949_2.png) [@Jack\_Roberts](https://community.forestadmin.com/u/Jack_Roberts)\
**Post date:** [March 13, 2021, 3:56pm UTC](https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088/1 "2021-03-13T15:56:51Z")

</div>

After updating our staging environment to the latest FA and updating node to version v15.11.0 I am seeing the errors below.

**Environment** :

```javascript
$ npm outdated
Package Current Wanted Latest Location  
chalk 1.1.3 1.1.3 4.1.0 roadsync2
cookie-parser 1.4.4 1.4.4 1.4.5 roadsync2
debug 4.0.1 4.0.1 4.3.1 roadsync2
dotenv 6.1.0 6.1.0 8.2.0 roadsync2
express 4.16.4 4.16.4 4.17.1 roadsync2
express-jwt 5.3.1 5.3.1 6.0.0 roadsync2
forest-express 7.10.1 7.10.1 8.0.5 roadsync2
morgan 1.9.1 1.9.1 1.10.0 roadsync2
pg 8.2.2 8.2.2 8.5.1 roadsync2
sequelize 5.15.2 5.15.2 6.5.0 roadsync2
undefined

```

**Errors Below:**

```javascript
$ npm start

> roadsync2@0.0.1 start

> node ./server.js

[forest] 🌳🌳🌳 The objectMapping option appears to be missing. Please make sure it is set correctly.

{}

Your application is listening on port 3310.

Your admin panel is available here: https://app.forestadmin.com/projects

OPTIONS /forest/sessions 204 0 - 2.314 ms

[forest] 🌳🌳🌳 The Liana has not been initialized to enable the authentication.

{}

POST /forest/sessions 401 92 - 12.396 ms

[forest] 🌳🌳🌳 The Liana has not been initialized to enable the authentication.

{}

POST /forest/sessions 401 92 - 2.119 ms

[forest] 🌳🌳🌳 The Liana has not been initialized to enable the authentication.

{}

POST /forest/sessions 401 92 - 1.490 ms

[forest] 🌳🌳🌳 The Liana has not been initialized to enable the authentication.

{}

POST /forest/sessions 401 92 - 1.440 ms

[forest] 🌳🌳🌳 The Liana has not been initialized to enable the authentication.

{}

POST /forest/sessions 401 92 - 1.391 ms

[forest] 🌳🌳🌳 The Liana has not been initialized to enable the authentication.

{}

POST /forest/sessions 401 92 - 1.432 ms

```

---

<div class="post-metadata">

**Author:** ![Guillaume\_Cisco](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaume_cisco/32/918_2.png) [@Guillaume\_Cisco](https://community.forestadmin.com/u/Guillaume_Cisco)\
**Post date:** [March 15, 2021, 9:35am UTC](https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088/2 "2021-03-15T09:35:14Z")

</div>

Hello @Jack_Roberts,

It looks like you migrated to the V7 version of Forest Admin.  
Did you correctly follow the [migration steps](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7) in the documentation?

Your issue is related to the [breaking changes](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7#liana-initialization-new-parameters)

```javascript
The liana initialization now takes objectMapping and connections as parameters (see lines 8 and 9).

```

Let me know if it helps 🙂

---

<div class="post-metadata">

**Author:** ![dmullen](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@dmullen](https://community.forestadmin.com/u/dmullen)\
**Post date:** [June 9, 2021, 3:52pm UTC](https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088/3 "2021-06-09T15:52:02Z")

</div>

Thank you for this info, Guillaume. I want to “complain” a little bit, though:  
On the [“Upgrade to v7” page, under the “Upgrading to v7” section](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7#liana-initialization-new-parameters), it says, "To upgrade to v7, simply run: `npm install forest-express-mongoose@^7.0.0`". I did that and then closed the FA upgrade info page. It would really prevent a lot of misunderstanding if that sentence said, “To upgrade to v7, run the following and then update your files as shown in the ‘Breaking Changes’ section below:”

“To upgrade…simply run” means you only have to run one thing. “To upgrade, run the following and update your files” means you have to do a few things. I’m not trying to be a pain in the rear, I just hope that making things more clear to people might be helpful to FA and its users. Cheers! -DM

---

<div class="post-metadata">

**Author:** ![anon39940173](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon39940173](https://community.forestadmin.com/u/anon39940173)\
**Post date:** [June 10, 2021, 9:23am UTC](https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088/4 "2021-06-10T09:23:04Z")

</div>

Hello @dmullen

Indeed, the phrasing in the doc was quite unclear.  
I just updated the documentation.

Thank you for the suggestion!

---

<div class="post-metadata">

**Author:** ![dmullen](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@dmullen](https://community.forestadmin.com/u/dmullen)\
**Post date:** [June 10, 2021, 12:45pm UTC](https://community.forestadmin.com/t/the-objectmapping-option-appears-to-be-missing/2088/5 "2021-06-10T12:45:27Z")

</div>

That’s great, thanks for updating it!