11842955 - Schema Handling Update For Database Fields
Updated how we handle schema when dealing with an external ERP. Over the last two years, we've been expanding field lengths as we run into issues. The problem with doing it this way is that this means that sometimes we have fields that are longer than the ERP supports. For example, Customer numbers are length 10 in
M1, 23 in
Sage 100, and 24 in
QuickBooks. Since 24 was the longest we'd seen, BD Engine used 24. This means that you can create customer # TESTIMTOOLONG in our system and then it will blow up writing to M1. As of this build, we'll create the database with BD Engine defaults but once you create an ERP connector, the system will automatically alter the database to match.