select2_from_ajax / fetch operation specify key

[emogeekface]

Is there any way to specify that a different key is used for a select2_from_ajax field instead of id?

I know that using a select2_ajax filter, you can pass in select_key - is there anything like this for the field?

Alternatively can you set what is returned from the fetch operation?

[pxpm]

@emogeekface hey there.

I don't think it's needed for the fetch operation as you can control what gets sent with:

public function fetchSomething()
{
    return $this->fetch([
        // configure the fetch here, search operator, columns etc
    ]);
}

Check all options and examples here: https://backpackforlaravel.com/docs/5.x/crud-operation-fetch#how-to-use-1

Let me know if this is not what you are looking for.

Cheers

[emogeekface]

@pxpm ah ok, so is there a columns argument I can pass to that? E.g.

public function fetchSomething()
{
    return $this->fetch([
        'columns' => ['something', 'something_else']
    ]);
}

or do I need to do it within the query argument? The documentation only shows these:

return $this->fetch([
            'model' => \App\Models\Tag::class, // required
            'searchable_attributes' => ['name', 'description'],
            'paginate' => 10, // items to show per page
            'searchOperator' => 'LIKE',
            'query' => function($model) {
                return $model->active();
            } // to filter the results that are returned
        ]);

[pxpm]

Sorry @emogeekface I may have missed your question.

That option to provide a different key is not applied to select2_from_ajax field, it's locked to get the actual "model" key:

<option value="{{ $item->getKey() }}" selected>
                {{ $item->{$field['attribute']} }}
            </option>

So the only way to use other key is if that $item is effectively using other key defined in the model.

An easy way out is to publish the select2_from_ajax.blade.php with php artisan backpack:field select2_from_ajax_custom_key --from=select2_from_ajax (you need backpack generators installed to run this command, or you can do it manually.)

It will publish a copy of the ajax field to your resources folder, you can then modify the blade file to check for $item->{$field['custom_key']} instead of ->getKey() and getKeyName().

You then use your own select from ajax with custom key when you need it, without overriding the core backpack field. That way even if we introduce that ability as a core in future, at most you would just need to change the custom_key to whatever key Backpack decides to use and you will be good to go 👍

Let me know if I am on the right track or missing something.

Cheers

[emogeekface]

OK, Thanks @pxpm makes sense :-)

[jcastroa87]

I'm closing this issue due to inactivity. If you need further assistance or have additional questions, feel free to reopen this issue or create a new one. We're here to help!