Adding required logic to custom fields

💬 General Discussion
1

I was following the doc to add required logic for my custom fields as below.

image
image944×497 23.6 KB

On the app side, I made sure that the metadata has been loaded.
image
image1026×710 41.6 KB

In contract add/edit view, the logic is not triggered. I still can save contracts which do not meet the validation rule. Any ideas?

P.S. Both wecom_approval_id_c and contract_payment_method_c are custom fields.

2

Any relevant errors in the console?

3

No, I don’t see any error messages from the browser console.

4

Without any clues, it will be hard to find the problem.

You can try debugging the front-end, but that requires quite some skill, it’s not for everyone.

Or simply open an Issue on Github and hope that the devs take a look at it.

5

Do you have any link or documentation about how to set up dev environment? The Developer Guide focuses on application level. Shall I just build a dev bundle and deploy it so I can debug it in browser console?

6

I think there may be an error in the doc, not-equal operator should have the next line as:

Values=> [‘val1’]

Please note plural values and the [] even if only one value.

Please check the Logic Operator doc here:

https://docs.suitecrm.com/8.x/developer/extensions/frontend/logic/operators/

Mark

7

Same issue. I think I need to set up a dev environment to debug it.
image

8

@wannadream

Arrg, that’ll teach me, I just re-checked your initial screenshot and then re-checked on my 8.9 install.

Your fields are AOS_Contracts fields, it looks here like Contracts are still running under the legacy Suite7 and haven’t yet been converted to Suite8, hence none of this will work as yet.

Mark

9

Thanks for letting me know.

10

@markbond I am just wondering if there is an ETA of the migration. I checked the roadmap but did not find anything.

11

I have no idea Im afraid, their roadmap is very vague and I have no insider info.

Regards

Mark