# Field value change best practices **URL:** \ **Category:** Nextworld Platform\ **Created:** [April 29, 2026, 6:12pm UTC](https://community.nextw.com/t/field-value-change-best-practices/1994 "2026-04-29T18:12:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bethany.k](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/bethany.k/32/111_2.png) [@bethany.k](https://community.nextw.com/u/bethany.k)\ **Post date:** [April 29, 2026, 6:12pm UTC](https://community.nextw.com/t/field-value-change-best-practices/1994/1 "2026-04-29T18:12:59Z")
I have some questions around handling field value change logic. 1. Is Option 1 or 2 better? Or does it not really matter? 2. For Option 2, will the logic run in the order I have on the app? **Option 1: Wrapper LB for FVC** In this scenario, you have one LB on the FVC event and it calls all relevant LBs that need to happen on FVC. ![image](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/2X/2/2481a1346e63ff3ce9494c00004c905cecdd35f6.png) **Option 2: Individual LBs for FVC** In this scenario, I add multiple FVC events for every logic block that needs to happen on FVC. ![image](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/2X/7/7e62c545115d464b8e151b1eda71250567036396.png) ---
**Author:** ![joeyates23](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/joeyates23/32/202_2.png) [@joeyates23](https://community.nextw.com/u/joeyates23)\ **Post date:** [April 29, 2026, 6:20pm UTC](https://community.nextw.com/t/field-value-change-best-practices/1994/2 "2026-04-29T18:20:18Z")
So it’s probably dependent on you philosophy on encapsulation, code organization and so on for which one is better. But I don’t think technically one is much better or worse than the other. In option 2, that is correct, the order they are in the subtabe is the order they will be run. ---
**Author:** ![bethany.k](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/bethany.k/32/111_2.png) [@bethany.k](https://community.nextw.com/u/bethany.k)\ **Post date:** [April 29, 2026, 6:22pm UTC](https://community.nextw.com/t/field-value-change-best-practices/1994/3 "2026-04-29T18:22:40Z")
@joeyates23 thank you! And I want to confirm there are no performance differences between using one versus the other? I am pretty sure, I heard there isn’t, but want to confirm. ---
**Author:** ![kendra.b](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/kendra.b/32/110_2.png) [@kendra.b](https://community.nextw.com/u/kendra.b)\ **Post date:** [April 29, 2026, 6:27pm UTC](https://community.nextw.com/t/field-value-change-best-practices/1994/4 "2026-04-29T18:27:24Z")
Joe makes good points, but there is a little more. If you want _control_ you choose option 1. With option 1 you can decide if you want to continue running the others when the first one has problems - do you want all the problems in one go or do you want to abort as soon as something goes sideways? With option 1 you can do either. With option 2 they will all run. There is no measurable performance delta between the choices other than the ability to abort sooner. It’s one trip from the browser regardless. ---
**Author:** ![joeyates23](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/joeyates23/32/202_2.png) [@joeyates23](https://community.nextw.com/u/joeyates23)\ **Post date:** [April 29, 2026, 6:29pm UTC](https://community.nextw.com/t/field-value-change-best-practices/1994/5 "2026-04-29T18:29:49Z")
Yeah definitely fair points for different levels of control between the two and probably also depends on some use cases where one can make sense over the other.