NEW Can use constant into param of a custom calculated export field #31783
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow usage of a method param that is not part of the $obj from the sql request.
The issue I encontered is the usage of order's LibStatut method that required a $mode param that can't be fetched from the sql request obj.
This would be the code for the export declaration :
$this->export_special_array[$r] = array(
'orders.fk_statut'=> [
'rule' => 'compute',
'class' => 'Commande',
'classfile' => '/commande/class/commande.class.php',
'method' => 'LibStatut',
'method_params' => ['orders_fk_statut', 'orders_facture', '1'],
],
);
We can see that the first two params will come from the $obj, but the third one will be used for it's value (in this case '1').