Skip to main content

No Code Customizations

  • November 26, 2025
  • 1 reply
  • 32 views

Forum|alt.badge.img

What’s some opinions on organizing No/Low Code Customizations. ( new added fields, customization creates fields, new checkboxes, minor changes , etc).

Would you roll them all into one , with multiple customized screens, separate them by module( sales orders, opportunities, etc). Or one project per change? 
 

I am trying to figure out what makes the most sense for years down the road with the best organization practices or potential issues.  

1 reply

bwhite49
Captain II
Forum|alt.badge.img+10
  • Captain II
  • November 26, 2025

We do one project for no code. We call it workflow or navigation tools. 

This makes it easier to review if the workflow needs to be updated for each screen after an update. Also reduces the risk of conflicts, as you can only have one project modifying workflow per screen. 

I don’t think there are any downsides for using one project either.