You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I am building up a Collection Structure via an import script. I want to search on exact names and filter on parent_id to get the exact first hit so I can build up the collection tree.
Actual Behaviour:
Since the names are hidden in the attributes field and no handle or some identifiable name is stored directly in the table, you can only search for the name via Scout. But in the database index you cannot filter on parent_id. Also it not always gives the correct result; if you Collection name has spaces in it, the search results are based on a word level. You cannot set it to match the whole string.
I also now have to cache the Parent CollectionIDs in the import script. I rather lookup it fresh so I know I have the correct one, but that's not possible.
We have discussed this previously, so this is a good reminder. We wanted to pull out the name attributes (and maybe handle, if required) into dedicated fields.
Expected Behaviour:
When I am building up a Collection Structure via an import script. I want to search on exact names and filter on parent_id to get the exact first hit so I can build up the collection tree.
Actual Behaviour:
Since the names are hidden in the attributes field and no handle or some identifiable name is stored directly in the table, you can only search for the name via Scout. But in the database index you cannot filter on parent_id. Also it not always gives the correct result; if you Collection name has spaces in it, the search results are based on a word level. You cannot set it to match the whole string.
I also now have to cache the Parent CollectionIDs in the import script. I rather lookup it fresh so I know I have the correct one, but that's not possible.
Steps To Reproduce:
https://docs-v1.lunarphp.io/core/reference/collections.html#collections-1
I would love to see a name and handle in the Collection table. Just like in all other models. And use attributes for translations and other metadata.
The text was updated successfully, but these errors were encountered: