-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sub-selecting custom fields #419
Comments
How did you solve this? |
It pained me to do this but I moved the code that resolved these custom fields to where I was trying to get these fields. 😢 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I am sorry if I am missing something big here! I do not even see why this would work but I am completely lost how to go about it :)
I have a big operation that I need to do on the server. It is completely disconnected with the front-end request. I am trying to get some custom fields in a subselection in a prisma query on the backend. This custom field is in the schema but it is not in the prisma data-model; that is why I don't see why it would even work in the first place.
In the picture below, what I have highlighted in the editor is the custom field.
I am getting this error:
My question is: is it possible to use prisma at all to access these custom fields on the server? If not, can you point me in the right direction? Thank you so much.
The text was updated successfully, but these errors were encountered: