Bursting Smart Notifications Based off a Second Infoset.

juergen-erbe

One of the things I'm attempting to figure out and can't find documented anywhere is how to get an Infoset to appear in the drop down list when you are attempting to burst a notification based on an ID column in the 'data' Infoset.

As an example, I have an Infoset set up that lists everyone who has a dependant with a 'bogus' SSN. I want to send them a notification out of LBI that they need to go in and make corrections.

I've got it currently so that I can burst the notification based off an email column in the Infoset itself, but that causes the column to be listed in the email as well. So what I'd like to do is set up a second infoset which is just employee #'s and email addresses and cause the notification to use the employee # in the 'data' infoset to tie to the employee # in the 'distribution' infoset.

But I can't seem to get the 'distribution' infoset to show up in the dropdown menu where you'd pick which infoset to use for this. I've marked the email column in the distribution infoset as 'burst on' I've given the employee # columns in both infosets a matching category. And although I didn't see anything in the manual indicating it, I've even made sure that 'EMAIL' was part of the name of the infoset since all the infosets that ARE showing up have that trait.

But I can't seem to find the trick. Anyone else know?

unknown

This has worked for us. On the bursting infoset (empid, email) - the email column is 'email' type. we also make sure the category on the key (empid) is set to the same category on both the report infoset and the bursting infoset. i think at one point the common categories was used to help join the two infosets. don't know if it's still necessary, but we still do it.