I have looked on the forum and haven’t found a single post or more information for “leveling” customization on the Customization Projects Screen.
Is there a good way to properly level customization? What kind of approach should someone have when dealing with multiple customizations for the same screen?
Solved
Customization Level: What is the best approach when labelling customization levels?
Best answer by Naveen Boga
Dependency on Other Customization: When a customization package relies on another customization, it becomes necessary to specify the package levels to ensure package publish smooth.
Importance of Changes: It is strongly advised to assign the HIGHEST level to packages containing critical and significant changes. This practice ensures that these vital modifications take precedence and are implemented effectively.
Default Level: In the absence of a specified package level, the system will automatically consider it as Level 0.
By utilizing Package Levels effectively, we can streamline the customization process, minimize conflicts, and leading to a more efficient and seamless deployment of customized package solutions.
+19Dependency on Other Customization: When a customization package relies on another customization, it becomes necessary to specify the package levels to ensure package publish smooth.
Importance of Changes: It is strongly advised to assign the HIGHEST level to packages containing critical and significant changes. This practice ensures that these vital modifications take precedence and are implemented effectively.
Default Level: In the absence of a specified package level, the system will automatically consider it as Level 0.
By utilizing Package Levels effectively, we can streamline the customization process, minimize conflicts, and leading to a more efficient and seamless deployment of customized package solutions.
Naveen B - Acumatica MVP 🏆 | Independent Developer for Hire 🚀 ⏩ https://www.linkedin.com/in/boga-naveen-kumar-54079a66/
Hi
Acumatica provides customization projects that allow you to group related customizations together. Create separate customization projects for different modules or logical groupings of customizations. Additionally, consider using versioning within the customization projects to track changes over time.
Prioritize the customizations based on business impact, urgency, and complexity. Start with high-priority and straightforward customizations before moving on to more complex ones.
Use clear and consistent naming conventions for customizations, fields, and other objects. This makes it more easier to understand.
Regards,
Sweta
1 person likes this
+3Just an example of how I do Package levels:
- Customization packages from my VAR get higher priority (so a lower number, say 1-5). I don’t want to mess with their builds, and I would struggle to troubleshoot them if I did
- Next (6), I have a customization package that I use with all my custom fields. That way, other customizations can see them downstream
- Finally (7+), other packages, like Workflows
I’m no expert, but this strategy has seemed to work well so far. Best of luck!
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.