@chandlervdw You might be able to achieve that using a Request Pipeline function. I'm doing something similar for auto-generated slugs.

Do you happen to have an example?

I'm out for lunch at the moment so I don't have my computer with me, but it goes something like this... 1. Set up vanityURL field WITHOUT unique constraint. 2. Create new request pipeline function that gets called whenever a campaign is created or updated. 3. In this function, write a query to see if other campaigns in the same organization have the same vanityURL. 4. If others have the same vanityURL, either return an error or generate a different one. Your choice.

I found the docs for it! Thanks

@chandlervdw Yeah, I can see why you'd say that. I'm actually using my own server for this and calling it as a webhook.

@Pkmmte so when you call it as a webhook, do you still have to make requests back to Graph.cool for relationship data or can you somehow add it to the pipeline payload?

@chandlervdw I have to make requests back to Graphcool if I want to check something not included in the payload. In my case, yeah, I make a query to check if there's an existing duplicate. It's not efficient but it's the best thing I found that works.

man, it seems like they should allow you to edit the request pipeline payload, much like they do with server-side subscriptions

please ask broader questions in the forum: https://www.graph.cool/forum/ unfortunately, I can't keep up with all messages here 🙂

done. thanks!