Extrafield sql error after upgrade V20

sonikf · December 22, 2024, 11:41pm

You should always check the ChangeLog and test before upgrading.

Dolibarr/dolibarr/blob/3cefab32d51e66cea31f97e60341a0bb58906573/ChangeLog#L597


      
          QUAL: the config_extended of phpstan will be kept on apstats only for the
          QUAL: The signature for all ->delete() method has been modified to match
          QUAL: Use phan to help detect new issues (#27706)
          QUAL: use real time when creating action from list
          QUAL: replace hard-coded dictionary IDs with constants (#29501)
          
          WARNING:
          --------
          
          The following changes may create regressions for some external modules, but were necessary to make Dolibarr better:
          * If a filter is defined into and extrafields "Select from a table", this filter MUST use the Universai Search Filter syntax (field:=:value) instead of field=value.
            See https://wiki.dolibarr.org/index.php?title=Universal_Search_Filter_Syntax
          * The parameter $filter of methods fetchAll() does not accept array of SQL commands but must be a string of an Universal Search Filter syntax.
            See https://wiki.dolibarr.org/index.php?title=Universal_Search_Filter_Syntax
          * The use of 'customurl' into $filter has been removed. Must use the USF syntax.
          * Some API HTTP return code were moved from 401 to 403 to better follow REST specification.
          * More class properties (with old name in french) are now deprecated in favor of the property name in english.
          * dolibarrtriggers class VERSION_XXX constants have been deprecated. Please use array dictionary VERSIONS['XXX'].
          * Properties ->date_update and ->date_modification were merged into date_modification.
          * All CLI tools (into /scripts) return a positive value to the shell if error (0 remains success) for a better
            cross platform compatibility. On linux the exit(-1) was caught as 255, it may be now exit(1) so will be caught as 1.

so from now on the correct syntax will be

product:ref:rowid::(ref:LIKE:'%pack_box_carton%')