# Generate forestadmin-schema.json manually

**URL:** <https://community.forestadmin.com/t/generate-forestadmin-schema-json-manually/5961>\
**Category:** Help me!\
**Created:** [February 7, 2023, 11:35pm UTC](https://community.forestadmin.com/t/generate-forestadmin-schema-json-manually/5961 "2023-02-07T23:35:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon75040465](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@anon75040465](https://community.forestadmin.com/u/anon75040465)\
**Post date:** [February 7, 2023, 11:35pm UTC](https://community.forestadmin.com/t/generate-forestadmin-schema-json-manually/5961/1 "2023-02-07T23:35:54Z")

</div>

Hi,  
With the default setup, forestadmin-schema.json is generated locally.  
All the developers in my team constantly have diff on the generated file (could it be because we all have locally slightly different databases due to migrations run in different orders?).  
So all pull requests are polluted by hundreds of line of difference in this file.  
How can I avoid this?

I wanted to skip automatic generation of forestadmin-schema.json and to generate it manually but the command `forest schema:update` doesn’t work.  
I get the following error: `The liana is incompatible for update: Your project is not compatible with the `lforest schema:update` command. You need to use an agent version greater than 7.0.0.`.

packages versions:

- “@forestadmin/agent”: “1.7.1”
- “@forestadmin/datasource-sql”: “1.2.0”
- “forest-cli”: “3.0.11”

---

<div class="post-metadata">

**Author:** ![Alban\_Bertolini](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/alban_bertolini/32/1077_2.png) [@Alban\_Bertolini](https://community.forestadmin.com/u/Alban_Bertolini)\
**Post date:** [February 8, 2023, 9:05am UTC](https://community.forestadmin.com/t/generate-forestadmin-schema-json-manually/5961/2 "2023-02-08T09:05:19Z")

</div>

Hello,  
Unfortunately the forest-CLI is not compatible with your agent, it is planned in the roadmap to integrate it soon :).  
For your problem, we will solve it very quickly! I will create a high priority bug.  
I’ll come back to you as soon as it’s corrected.

---

<div class="post-metadata">

**Author:** ![Alban\_Bertolini](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/alban_bertolini/32/1077_2.png) [@Alban\_Bertolini](https://community.forestadmin.com/u/Alban_Bertolini)\
**Post date:** [February 13, 2023, 3:00pm UTC](https://community.forestadmin.com/t/generate-forestadmin-schema-json-manually/5961/4 "2023-02-13T15:00:10Z")

</div>

Hello,  
We are merging a [fix](https://github.com/ForestAdmin/agent-nodejs/pull/626#pullrequestreview-1295777451). Please install the last release to fix your issue 🙏

---

<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:** [February 13, 2023, 3:03pm UTC](https://community.forestadmin.com/t/generate-forestadmin-schema-json-manually/5961/5 "2023-02-13T15:03:51Z")

</div>

and another for the CLI: [fix(schema): use forest-express schema format for CLI compatibility by romain-gilliotte · Pull Request #622 · ForestAdmin/agent-nodejs · GitHub](https://github.com/ForestAdmin/agent-nodejs/pull/622)

(as you reported two different issues)