I have a question about Bursting with Conditions and/or Combines. I have a SN that has 2 Conditions (has new items, and has deleted items). I also have a Combine that will be true if one or more of the Conditions are true.

The problem that I've found is that even though I don't have any new or deleted items, the SN will still burst and deliver the emails. Does anyone know if there are issues using Bursting with Conditions and/or Combines?

Thanks.

Bill

hey Bill, saw your post on Lawson Community too, thought Id reply the same just to keep the knoledge base here, going:



Bill,

Ive had mixed success with Has New Items. In theory its the coolest condition.

First thing I would do is check if you have a datetime stamp in your infoset and have the Unique Record defined as Unique Row, if so every row will be new every time.

If thats not the case, set the infoset that your Notification is based off of to be "Larger than 20,000 Records", even if it isnt that big. What this does is creates a physical table in the SN repository to store the infoset records. Once youve done that if you are still seeing the issue, query that table and look at the field ROWISNEW. The table name will be INFOSET_[ID], where [ID] is the ID number of the infoset. You can find this in the URLs link next to the infoset in Working With InfoSets. Update your infoset and see if this table changes.

please reply with your results.

hth,
matt

That's a good idea. I have done the same...

Hi Matt,
There is a date field, not a datetime field. Just to be certain, I changed the data type in the infoset to string. Still getting updates...

I also checked the 20,000 records option. After first updating the table, all the rows have a 1 in the ROWISNEW field. Subsequent updates will have the original rows with a 0 in the column, but also the same number of new rows with a 1 in the column. Of course, I still get updates. Should I see both sets of data?

Bill

I dont believe you should see both sets, however you may want to check with Lawson on that. What is th drop down on Unique Row set to? If Unique Key, which fields have you set as Keys?

I have it set to 'No Filter'. The keys are on Company, PlantCode, and SalesRep.

I typically use Unique Key or Unique Row. In this case, Id suggest using Unique Key and see if that resolves the situation.

Same results with Unique Key or Unique Row.

I've opened a case with Lawson. I'll let you know what i find out.

The answer:
Don't check 'Show all rows (not only those that meet condition)'. Checking this will always count the condition as true. Live and learn...

However, I seem to have another issue. In this same SN, I have a Fact, 2 conditions, and 1 combine. The combine is set to '1 or more of them are true'.

What I want to happen is on an add or delete, emails burst with the fact table, and both of the conditions displaying either what was added/deleted or the default text when the condition is false.

What is happening now is with the conditions set to display 'Default', I get no bursting. If I set them to 'Do not display', I will get emails. The combine in both instances is set to 'Default'.

Any thoughts?

I spoke with Lawson again about this situation. It appears that what I'm attempting to do won't work within SN.

I have chosen to handle the adds/deletes at a database level, and then have the SN simply read that data.

Thanks for your help.

Bill