Can't get RecordFinder, using useRelation=false, to work properly

[climao]

I have Members (hasMany Payments) and Payments (belongsTo Member).

The Member Form uses a partial to render the Payments relation:

    ...
    payments:
        label: 'bitstuff.payments::lang.plugin.name'
        type: partial
        path: payment_fields
    ...

_payment_fields.htm:

<?= $this->relationRender('payments') ?>

The Payment Form uses a RecordFinder to choose which member is making the payment.
Of course, if it is being used from a Member form, the member is already known, so when a Member issues a Payment the payment fields.yaml uses this:

...
    member:
        label: 'author.payments::lang.payment_member_label'
        nameFrom: member_number
        descriptionFrom: member_name
        list: $/author/member/models/member/columns.yaml
        span: left
        type: recordfinder
        useRelation: false                           <=== To just use the member's ID
        modelClass: Author\Member\Models\Member      <=== Class of model to use
...     

The problem is that, in the Payment form, the Member does not get initialized properly (i.e. it is always null).

I dug a bit and noticed that in Backend\FormWidgets\RecordFinder.php the getLoadValue() function uses:

    public function getLoadValue()
    {
        ...
        
            $value = $this->modelClass::where($this->keyFrom, parent::getLoadValue())->first();
        }

        return $value;
    }

which, in my case, is the source of the problem, because $value is always null.

If I change it to:

    ...
    $value = $this->modelClass::where($this->keyFrom, parent::getLoadValue()->{$this->keyFrom})->first(); 
    ...

everything works just fine!

Of course, I am assuming there is something wrong with my code...

What am I missing here?

---

This is running in the Winter backend using:

• Winter CMS build 1.1.7
• PHP 7.3
• MySQL 5.7.

[climao]

I found the problem!

I have overridden the manage_form backend partial and was using a Member instance instead of a Member id.

If anyone stumbles into this, the partial has only one difference, which is updating the field value before calling render():

            <div class="modal-body">
                <?php $relationManageWidget->getField('member')->value = basename(Request::path()); ?>
                <?= $relationManageWidget->render() ?>
            </div>

It's working just fine.
I'm not sure this is the right way to do it, though.

Any comments would be appreciated.

[LukeTowers]

Only skimmed over the description but as soon as I saw the name of the field being set to member I can tell you what's going wrong.

If you set useRelation: false, then you are now dealing with just an ID value. So, the name of the field (and thus the attribute that the data is being stored and retrieved from) should be the name of the column the data is actually being stored in, i.e. member_id, not member.

[LukeTowers]

See wintercms/docs@a8584bb

[climao]

Thank you for clarifying this! It was not clear in the original doc.

My use case, however, in none of those you mentioned.
The thing is I want to fill the member_id with a default value to be used by the RecordFinder.
To do this, I'm overriding the _manage_form.htm backend partial.
Is this the best way to do it?

[LukeTowers]

No, it's not. If you want to set a default value then do it statically in the fields.yaml or dynamically through the various methods to extend form fields: https://wintercms.com/docs/backend/forms#extend-form-fields

[climao]

The problem is that the default value of this depends on the selected Member.

Please take a look at the picture on my first Post. The red arrow shows what I'm trying to do.
"Mickey Mouse" should be the default (for "Beneficiário") in that case.