Hi Paul,

This is a known issue and is on the 'fix' list. You will probably find that if you repeat this process immediately after logging into CRM that you do not get this error, it only happens when the user has added something elsewhere prior to adding the note.

This was reported back in 2019R1 and was still present in R2.

I haven't fully tested in 2020R2 as there is another show stopper if your Custom Entity has workflow, where any field actions on the primary rule are ignored and the fields are null after save (set column value or display field for amendment)!!

As far as your error is concerned I'd recommend logging with Sage but refer to it as an existing issue.. They can then provide you with their allocated code and you'll be able to see if it is in the resolved issues in the release notes.

Roger

Thanks Roger.  I tried creating a note immediately after logging in - it still caused the error.

I think I'll just write my own asp page for this - you can grow old waiting for Sage to fix anything.

I have a client that had this issue.  It was fixed in 2020R2

From Release Notes for Sage CRM 2020R2

"CRMS-159 Customization An unexpected event error occurred when a user entered a note on a custom entity record. This issue is fixed."

Thanks, Joel.  Nice to know it has been fixed; unfortunately the end user has a Sage 200 integrated system and I believe that CRM 2020 R1 is the latest that can be used with this.

Correct, Sage 200 CRM is no more (2020 R1 is the last of its line). The customer will in the future need to think about migrating to using Qnect200 and Standalone CRM (there are scripts and tools available to help convert them from Sage 200 CRM to Standalone) in order to have a Sage 200 <> CRM Integration

And just to add Qnect 200 has now been tested and is compatible with the new Sage CRM 2021 R1 release.

Julian

The general policy for Sage CRM is that patches are only provided where security is concerned or where there is a critical impact on the business. The policy is to fix bugs within the next available release where possible.   

Julian

Testing has 3 broad elements.  Functional change testing - this is where the new features are tested. Then key feature testing.  These first two types of testing are by humans.  Machine testing is used for general regression testing.  Each of the testing mechanisms uses scripts that are considered reasonable because of the changes that have taken place. Another level of testing takes place when a release candidate version of the software is sent to the integration teams to check the integration behaviour and APIs.  Each version we have released since 2018 has had over 30 user defined bugs identified and fixed.  In addition to those we fixed between 60 ad 90 other defects that have been identified internally but have not been reported by partners.  Each of the addressed bugs have to be tested.