Not really... you can change the available blocks on page load with the

blocks

property of field but I don't think this can be done dynamically like

@formConnectedFields

. Also, changing the available blocks won't affect the existing blocks, like remove previous blocks that are no longer "valid" in the current available blocks.

I see, thank you

you can't use the

related

browser feature to make this kind of relationship. you need regular browsers that save a belongsTo.

Try

$browsers

instead here

even if you give different names to the block editor fields depending on your condition?

do I need to change any other code elsewhere? I had the belongsToMany functions in the journey model for the relatedBrowser

Not sure, I will try this

I still see both editors

you want to select a single client, right?

yes 1 client and 1 category

same client and same category can be used in multiple journeys

ok so you need the client belongsTo relationship in

App\Models\Journey

the one you had earlier in

App\Journey

name your browser field

client

and same in the repository's

$browsers

array

the belongsTo relationship should be referencing

App\Models\Client

not

App\Client

too

ok, would you mind posting an issue on GitHub so we can look into it? Thank you

protected $browsers = ['client','category'];

    public function __construct(Journey $model)
    {
        $this->model = $model;
    }

    public function afterSave($object, $fields)
    {
        $this->updateBrowser($object, $fields, 'client');
        $this->updateBrowser($object, $fields, 'category');
        parent::afterSave($object, $fields);
    }

    public function getFormFields($object)
    {
        $fields = parent::getFormFields($object);
        $fields['browsers']['client'] = $this->getFormFieldsForBrowser($object, 'client');
        $fields['browsers']['category'] = $this->getFormFieldsForBrowser($object, 'category');
        return $fields;
    }

is everything here correctly changed up?

sure, I'll do that as soon as possible

you don't need any of the code in afterSave and getFormFields if you use the

$browsers

array

oh

Twill does it for you here https://github.com/area17/twill/blob/2.x/src/Repositories/Behaviors/HandleBrowsers.php

@formField('browser', [
        'moduleName' => 'clients',
        'name' => 'client_id',
        'label' => 'Clients',
        'max' => 1,
    ])

would the name now be client_id or still client? at the end of the day the idea is to save into a database column known as client_id

i've got the client_id in the fillable/translatedattributes within the model so that should be correct

No matter if client or client_id is the name, this is the error im getting

you have data in the related table for that browser name which conflict with your new configuration

name of the field should be client

in both the form.blade and model?

in the form and repository. client_id in the model's fillable is correct.

in terms of the category/categories module and database field called category, i've followed the exact same steps as the client one and it doesn't stick to form and save either, might have messed up somewhere with the wording of category/categories

Everything seems to have crashed altogether after doing the browsers instead of relatedBrowsers, Trying to get property 'journey_name' of non-object everywhere on front-end even when a twill/database record is present