Who's On?

	Membership:
	Latest: Kyle
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5220

	People Online:
	Visitors: 235
	Members: 0
	Total: 235

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

Some smart notes no longer working correctly

3 Replies

0 Subscribed to this topic

14 Subscribed to this forum

Sort:

Author

Messages

SueS

Basic Member

Posts: 20

8/3/2012 10:56 AM

We moved a new smart note into production and appear to have broken somethng for 5 other smart notes. When the new smart note went into production, these 5 smart notes stopped working correctly. They are huge and looks like it is just dumping the entire infoset without checking if the keys have changed.

I can see in the schedule administration that it runs everyday and it is doing an update/process everyday.

These 5 smart notes share the same infoset and no other smart notes use this particular infoset. The infoset is built with a DME query. Create notification from a local snapshot of this data is checked. The infoset has many different fields that are designated as "key" fields.

The notifications all have "tell me if data has new keys" and have several keyed fields on the notification. I also don't think it has anything to do with the notifications because we tried deleting one and re-adding it with the same results.

Has anybody had this happen to them and if so what was done to correct the issue?

Thanks.

Matthew Nye

Veteran Member

Posts: 514

8/4/2012 2:24 PM

"tell me if data has new keys" is very touchy. it uses a field that tracks the keys every time you update. because of this its very difficult to test. the best way to do this is:

* reset your infoset
* Update/Process the 1st time should indicated that all records are new
* make a change to the source data
* update/process a 2nd time should show the changes you just made

SueS

Basic Member

Posts: 20

8/6/2012 10:33 AM

I had tried that already but it is still acted as though all records are new.

Matthew Nye

Veteran Member

Posts: 514

8/6/2012 6:57 PM

if the infoset is set to "> 20,000 records", do a select from the table which should correspond to the infoset id (INFOSET_1024) and see what the ISNEW column values are set as.

honestly, it would probably just be easier to create this all from scratch is a reset doesnt solve your problem. youll most likely end up chasing this issue for days.