geroyche

not only so. it's also about whether the locale already exists or not. .locale(locale) to simply load an existing locale .locale(locale, opt) to load a newly created one .updateLocale(locale, opt)...

the datables state cookie has the filter information stored like this: {"iCreate":1331226938603,"iStart":0,"iEnd":1,"iLength":50,"aaSorting":[[3,"desc",1]],"oSearch":{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},"aoSearchCols":[{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true}, {"bCaseInsensitive":true,"sSearch":"(^|,)(Friedrichshafen)(,|$)","bRegex":true,"bSmart":false},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true}, {"bCaseInsensitive":true,"sSearch":"(^|,)(Agentur\ Holzheimer)(,|$)","bRegex":true,"bSmart":false}, {"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true},{"bCaseInsensitive":true,"sSearch":"","bRegex":false,"bSmart":true}] so columnfilterwidgets would have to somehow identify the state cookie, just as datatables does,...

ok, great. that removes the ambiguity from the specs. the feature itself, proactive reporting, seems to be broken however. we found an ongoing discussion here: [https://forums.developer.amazon.com/questions/97669/cant-make-changereport-work.html](https://forums.developer.amazon.com/questions/97669/cant-make-changereport-work.html) but so far nobody...