Hi Everyone,
We're currently running BC14 on-premise, and like many companies we are normalizing our C/AL code base and beginning the transition to AL extensions. Fortunately with the guidance of this community (and my "mad google skills") we've been able to develop and test AL extensions. I'm hoping the BC experts will once again bless us with their knowledge on a few topics:
1. AL Extension Best Practices
@Mark Anderson started a great discussion on this topic a little while back, and
@Jason Wilder had suggested to start with converting page customizations to page extensions in AL. This makes a lot of sense as these modifications are least likely to have other C/AL changes dependent on them. Following this logic, it seems that table extensions may be the last step of converting to AL. Based on the amount of customization in our database, it is not practical to convert and implement all changes at once. Additionally, our plan is to separate customizations of third party solutions into separate extensions from customizations to base BC. I am curious if anyone has a "roadmap" for the C/AL to AL conversion process, or any recommendations for best practices.
2. Implementation
We are aware of the implementation sequence for on-premise extensions: Publish, Sync, Install - and we have powershell scripts to facilitate this process which work well in our test database (thanks,
@Kyle Hardin). My question is what is the process for implementing an extension in a system with multiple NST servers? I suspect all 3 steps are not required on both NST servers - is there a specific order of events which should occur?
We appreciate any information you can provide on these topics!
Thanks
------------------------------
Chris Goebel
Programmer/Business Analyst
The Music People Inc.
Berlin CT
------------------------------