v8.2 : config param customPrefixDisabled not set for middletable

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • item
    Active Community Member
    • Mar 2017
    • 1476

    v8.2 : config param customPrefixDisabled not set for middletable

    Hi Yuri,
    it's not a bug for me but i have choose to section :

    step :
    add param in config:
    'customPrefixDisabled' => true

    create a new entity result name : entityName => OK

    relate created entity to a entity => result : middletable : cMiddleName. => must follow config param ?

    Expected : middletable must (for me) follow config param.

    i can't test on demo .. i think this param on demo is set to false.


    Maybe this can be important in futur for.. and of course we can edit the name.

    Best Regards
    Attached Files
    Last edited by item; 04-04-2024, 09:25 PM.
    If you could give the project a star on GitHub. EspoCrm believe our work truly deserves more recognition. Thanks.​
  • victor
    Active Community Member
    • Aug 2022
    • 727

    #2
    With 'customPrefixDisabled' => true you can delete c from Middle Table Name​ and your MiddleName will be exactly MiddleName. But without 'customPrefixDisabled' => true, the Middle Table Name will be always saved as cMiddleName (as well as the name of the custom entity or the name of the custom field in the system entity).
    Last edited by victor; 04-04-2024, 10:45 PM.

    Comment

    • yuri
      Member
      • Mar 2014
      • 8440

      #3
      I'll move the logic to the serverside.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment

      Working...