I have a client that started using CRM back in version 6.x.  Way back then, we created a table named JOB with a fieldname prefix of job__, i.e. the word "job" followed by two underscores.

This Job table is a critical part of the client's CRM database.  We've done extensive customizations to workflows, ASP pages, .Net DLL's and even custom ASP.Net web applications.  The table now has over 180 custom fields, all using this original prefix.

Today I tried to create a new field and got this error:

     Incorrect format of the field name: the underscore must be followed by a letter.

So my only option, if I want to add this new field to the JOB table, is to break the field naming convention of having all fields using the same prefix.  But doing this would almost certainly risk breaking some other area of CRM that assumes (logically!) that all fields share the same prefix.

Obviously vendors should never introduce "enhancements" that break existing client customizations, which this one clearly does.  So Sage should:

1. create a PATCH release that removes this requirement for any clients that need this feature
2. implement a more client- and partner-responsible version in some upcoming release that only applies this logic to new tables