Notifications process broken in new API client

We recently just had a problem where a user overwrote a profile that was tied to hundreds of servers using the new OpManager API client. So we lost alerting on individual drives, windows services, processes, etc. The problem is when they went to make a change to the profile they were using the new API. In the Old UI if you went to a server, clicked on notifications and clicked on edit the profile...the profile would list services and drives "specific" to that server. And you were only modifying that server. In the new API if you go to the same server, click notifications, and click edit the profile its opening up a bulk editor. And it lists nothing specific for that server. Is this expected behavior?