Zane,

I have not done development specifically with Sage 300 CRM. However, for our internal development needs we have a separate Sage 300 company configured with test data. We use that when necessary for unit testing that requires database interaction (creating orders in Order Entry, for example). Essentially, you will need to configure at minimum a separate database within Microsoft SQL Server for the "development" company. You may also need a separate development instance of Windows Server configured if you need to run the development Sage 300 company on a separate server from your production environment.

I hope this is helpful!

Thank you for the reply. That makes complete sense from an infrastructure standpoint. Do you know what the licensing options are for that? Does Sage allow and stand-alone installation for development without proper licensing?

From my knowledge of a test environment you would simply setup an instance of CRM in a folder called, for example, TEST and connect to a test Sage 300 company. So you would for example, have a url like this https://company.com/test/eware.dll instead of the https://company.com/crm/eware.dll