Custom modules makes legacy access

đź’¬ General Discussion
1

Hello Everyone,

I have created one custom module from the module builder. Its name “oe_Inventory”. I need access to the legacy module.

I have added my option of file “services/module/module_routing.yaml”

emails:
      index: false
      list: false
      record: false
    calendar:
      index: false
      list: false
      record: false
    oe_Inventory:
      index: false
      list: false
      record: false

Then repair & rebuild but it is not accessible to the legacy module.

screenshot-2022.09.05-12_23_55
screenshot-2022.09.05-12_23_551830Ă—786 30.3 KB

Thanks in advance.
Asif Khalyani

2

Here’s my notes from recently doing this… (it does work but a bit finicky)

go to:

config/services/module/module_routing.yaml

then repair→rebuild in admin ./bin/console cache:clear from cli

First of all, if you want it to use the legacy module set it to “false”, it seems counterintuitive as it’s called “legacy module routing” you’d expect it to be the opposite.

ALSO… all the module names in the file are in lower case ie: “accounts” when they are actually “Accounts” in SuiteCRM, so if you have a custom module, you’d expect it to be lower case. You’d be wrong. I have “PLNE_Planes” module and you have to enter it exactly as it is in SuiteCRM custom modules folder.

ALSO… do not “tab” in the file to line up the columns, will not work. Space bar only.

1 Like