Hi Morten
FindSubscribersAsync works the other way around. You send in the partial key to find all subscribers that subscribes to anything under that key. So if User_A subscribes to {contacts://notifications/content/1/5/8945/13354/13466/13491/13492/}, then you can use FindSubscribersAsync with {contacts://notifications/content/1/5/8945/13354/13466/} and it will return User_A.
We are currently reviewing the notification and subscription api to see if anything should change before it goes out of beta. FindSubscribersAsync is likely to change or at least get a clearer description and documentation.
/Jonas
Tnx Jonas.
Have you considered creating a metod that does the oposite (like I thought it did :-), so we can use it to administer subscriptions connected to nodes in the page tree?
/M
Hi.
I am trying out the new Subscription Key API that currently is in BETA, but I am having a issue with the method FindSubscribersAsync.
According to the documentation, this method should return users that match a subscription key, fully or partly (begins-with). I have trouble with getting any results from partly matches.
https://world.episerver.com/documentation/developer-guides/CMS/using-notifications/subscription_keys/
In my case I have created a subscription between User_A and a key {contacts://notifications/content/1/5/8945/13354/13466/} (path of pageIDs)
Later I try to get subscription users for another subscription key {contacts://notifications/content/1/5/8945/13354/13466/13491/13492/} (path to a page further down the structure)
The way I read the documentation the FindSubscribersAsync method should return User_A, since he subscribes to a key that partly macthes the key in question, but the method returns none...
Can someone please advise as of what I am missing?
/Morten