-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After migration from 7.14 to 8.6 - Contracts subpanel in Accounts does not work #10440
Comments
Found the problem. Somehow in the metadat of the subpanel the type of the ACCOUNT_CONTRACT was 'date' instead of 'relate': 'contract_account' => After changing it to 'relate' (and running reapair) the error disappears. |
Doesn't that need to be fixed here?: |
This issue has been mentioned on SuiteCRM. There might be relevant details there: |
@pgorod Yes, you are absolutely correct, but as I have a custom definition, I did not notice this. |
Yeah, I am glad that I went and checked. I figured that this was a very illogical thing to put in the file, so you wouldn't have any reason to do it, it probably came from the original file. And there is was, an 11+ year-old bug... |
Issue
After migration from SuiteCRM 7.14 to 8.6 the Contracts subpanel in Accounts gives an error in the browser console:
ERROR node_modules_angular…1a513b7cb4915e.js:1
TypeError: r.match is not a function
See attached file for the complete stacktrace. None of the other panels work until this panel is switched off again.
Possible Fix
No response
Steps to Reproduce the Issue
Context
I am trying to fid a contract through Accounts. The other way arround (Go to contracts and filter on account) seems to work fine.
The error stack that is reported in the browser console is attached.
crm.dlearning.nl-1717148537573.log.zip
Version
8.6.0
What browser are you currently using?
Chrome
Browser Version
Version 125.0.6422.77 (Official Build) (64-bit)
Environment Information
MariaDB 10.6.16, PHP 8.1.2
Operating System and Version
Ubuntu 22.04.4 LTS
The text was updated successfully, but these errors were encountered: