Rafał Dzięgielewski

@ZanderFoster could you try with `@adminjs/relations` @ 1.1.1? The ids provided to `findMany` are now filtered to exclude undefined and null values if such exist in the list.

@ZanderFoster I've just tested in our test app with `Organization` and `Person`: ```prisma model Organization { id Int @id @default(autoincrement()) name String persons Person[] @@map("organizations") } model Person { id...

It should work if you change `appId` to `app` - `@adminjs/prisma` uses relation names from schema to query the database. I think the sorting error you're getting is due to:...

Please share more information. Your description isn't very helpful.

You can create a custom component for the other dropdown and filter out results based on `props.record.params`. `props.record` holds the state of the form

Yes, I'll help you tomorrow morning when I'm at work. Currently on a phone and it's inconvenient to write code

This is the default Reference component for `edit` action: https://github.com/SoftwareBrothers/adminjs/blob/master/src/frontend/components/property-type/reference/edit.tsx Options are loaded on these lines: ```ts const loadOptions = async (inputValue: string): Promise => { const api = new...

change ```ts const loadOptions = async (inputValue: string): Promise => { const api = new ApiClient() const optionRecords = await api.searchRecords({ resourceId, query: inputValue, params: { 'filters.categoryId': props.record?.params?.categoryId, } })...

Are you 100% sure you're on version 7.5.9? 7.5.8 should've fixed this bug. Alternatively, could you try: ```ts const redirectUrl = h.resourceUrl({ resourceId: 'Workflow' }) ``` and see if it...

It looks to be a Railway integration issue of some kind since we haven't had similar issues with other hosting services. Especially this error: ``` The requested module 'adminjs' is...