# Summary field changes after deploy **URL:** \ **Category:** Help me!\ **Created:** [February 8, 2023, 9:33am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964 "2023-02-08T09:33:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 8, 2023, 9:33am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/1 "2023-02-08T09:33:55Z")
## Feature(s) impacted UI Changes deployment for Summary field ## Observed behavior When we deploy changes with “summary” from Staging branch, then no one from Client/Production branches received it ## Expected behavior Changes for “summary” field properly applies after deploy ## Failure Logs No logs ## Context - Project name: ytech\_admin - Team name: Operations - Environment name: Staging - Agent type & version: “forest-express-mongoose”: “^8.7.8” - Recent changes made on your end if any: I’ll describe below Hi. Think we had manually changes in “Summary” section **after** they are deployed on Client/Production (that’s bad, I know). Now UI changes works, but if they for “summary” - it’s not We need to have Staging branch as base for any branches, mb you can check it and revert. Thanks ---
**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:54am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/2 "2023-02-08T09:54:53Z")
Hello @heyMakar, What do you mean by “manually changes” ? Do you see your fields in the forestadmin-schema.json ? ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 9, 2023, 1:26am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/3 "2023-02-09T01:26:24Z")
Manual changes is when we go directly to the environment, and update it via “Edit layout” button Nope, there’s no changes in forestadmin-schema for UI, isn’t? ---
**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 9, 2023, 8:19am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/4 "2023-02-09T08:19:19Z")
To resume the situation, You have edited the layout of the “summary” collection on the staging environment and you want to apply these changes on the production environment ? If you want apply the staging layout changes you should use the CLI to push the modification on the production environment: `forest deploy`. Ofc, the staging environment must have production as origin. Tell me if it helped you 🙏 ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 9, 2023, 8:33am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/5 "2023-02-09T08:33:20Z")
It’s vice versa. We edited “Summary” on Production (which relies on Staging), and after we “deploy” (without pushing) new changes with “Summary” section from Staging to Production they are not received on Production env ---
**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 9, 2023, 9:56am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/6 "2023-02-09T09:56:51Z")
When you say “deploy”, is it the `forest deploy` command from the CLI ? I’m checking on your production env, and it never receives a deploy command. ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 9, 2023, 10:13am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/7 "2023-02-09T10:13:58Z")
sorry for confusing you. As i said, we have changed separately Production branch (without changes from Staging branch). When we do new “Summary” section changes on Staging/Local dev branches and send them via `forest deploy` to Production branch, then they are not applied on Production env. ---
**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 9, 2023, 10:32am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/8 "2023-02-09T10:32:24Z")
Does the `forest deploy` return an error ? ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 10, 2023, 1:45am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/9 "2023-02-10T01:45:34Z")
nope, no errors. “Summary” changes from Dev or Staging just not showing on Production ---
**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 10, 2023, 9:38am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/10 "2023-02-10T09:38:29Z")
The latest update to your production was made on `02/02/2023 10:56:12`, indicating that no changes to the layout have been pushed since then. An uncommon configuration is present in your setup, as the Staging environment does not have the Origin set, while the Production environment has Staging as its Origin. Do you know why your Production environment has Staging as its origin ? In my opinion you must have Production as origin to Staging. To modify these references, go to the settings in the Environment section, select your production environment, and click on Set as production. ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/c/c7fac607f02b8b0706b7126a5edcb927f851d086.png) ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 10, 2023, 10:15am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/11 "2023-02-10T10:15:03Z")
wow, thanks for notice. I was not responsible for this setup. And now I see I can’t set origin for Staging environment, it’s just disabled with `You cannot set origin on Production environment` message. How we can fix that? ---
**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 10, 2023, 11:16am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/12 "2023-02-10T11:16:48Z")
You should “set as production” your Production environment. You should go on your Environment settings, click on the your production environment and click on “Set as production” button. You can follow this [doc](https://docs.forestadmin.com/developer-guide-agents-nodejs/deploying-to-production/environments#set-an-environment-as-production). ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 13, 2023, 3:21am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/13 "2023-02-13T03:21:12Z")
![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/b/b88b6c7537381a0482d60611b9c170e5a0ef1bd6.png) I can’t do anything with Staging env, set as production button/set origin select is disabled. Same for Production branch ---
**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, 8:33am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/14 "2023-02-13T08:33:35Z")
The button is also disabled for the PRODUCTION environment ? ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 13, 2023, 8:54am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/15 "2023-02-13T08:54:13Z")
yes, prod looks like this ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/f/f988ce90c2580144e53e2e6cb34e5ad1909b4da5.png) ---
**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, 9:22am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/16 "2023-02-13T09:22:17Z")
It appears that your environments are mutually locked, which may be a bug. To unlock, can you please confirm that we reverse the Staging environment to Staging and the Production environment to Production? ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 13, 2023, 9:36am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/17 "2023-02-13T09:36:34Z")
If you ask confirmation from me - sure, let’s do it. Is this can bring any destructive changes? ---
**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, 9:50am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/18 "2023-02-13T09:50:25Z")
Wa have made a manually change on our side. Please can you try again to “set as production” on your Production environment ? ---
**Author:** ![heyMakar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/heymakar/32/5411_2.png) [@heyMakar](https://community.forestadmin.com/u/heyMakar)\ **Post date:** [February 14, 2023, 1:50am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/19 "2023-02-14T01:50:51Z")
Now it’s ok, thanks. And we can use flow with push via forest cli? Eg. do local changes from Staging branch, then push this changes (via `push` command if it has UI changes, or just push schema to the server), and then (after test on staging) deploy them via `deploy` command or UI, right? ---
**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 14, 2023, 8:11am UTC](https://community.forestadmin.com/t/summary-field-changes-after-deploy/5964/20 "2023-02-14T08:11:29Z")
🥳 If you want to apply your layout changes from the staging environment to the production environment you can run [forest deploy](https://docs.forestadmin.com/developer-guide-agents-nodejs/deploying-to-production/forest-cli-commands/deploy). Here the [push](https://docs.forestadmin.com/developer-guide-agents-nodejs/deploying-to-production/forest-cli-commands/push) documentation to understand the difference.