Smart Notification Limits?

The only limit you will hit are those put upon you by your database repository (ie tablespace, quota, record size, etc). Ofcoarse the larger the row set the longer it will take to process and update. For any large record sets, be sure you tick the check box on the last step of the infoset editor to identify it as a Very Large Infoset (>20000 records), that then creates a physical table in the LawsonRS database that will hold those records. Otherwise all data is encoded to binary and stored in a field in a table.

hth
matt

When ticking the +20k infoset option, data is going to the LawsonSN DB and each infoset is referenced as INFOSET_xxxx (xxx being the infoset ID) by way of table.

It is generally not a good idea to have infosets with more than 20k rows as you will certainly run into performance issues. A good rule of thumb is to capture only the latest records from Lawson corresponding to the latest transactions depending on what you are notifiying. Also you may want to consolidate data at the query level (provinding you're using an ODBC datasource), this is also a good idea to leave this work to the query itself.