12.1p "Invalid comparator" Log Message

[dswarey]

Hello,

I have been updating one of the screens in our application and have encountered a log warning in the developer console that I am having trouble understanding. I have attached a screenshot of the warning below. I would appreciate any info on what this warning means. I have not been able to find a stack trace for this using Log.traceLogMessage in the Evaluate JS pane in the console, however I may be using the function incorrectly. I am specifically evaluating Log.traceLogMessage("/invalid comparator/").

The screen is composed of two ListGrids with a ValuesManager controlling several forms below them, along with Save, New, and Edit buttons tied to the ValuesManager. When Save is clicked, I use ValuesManager.saveData to save the data, then in the callback I am calling refreshData on both of the ListGrids. I've found that these warnings appear when Save is clicked and that the warnings do not appear if I remove the call to refreshData on the lower of the two ListGrids. Removing the call to the upper ListGrid changes nothing, but I can't find any difference between the two ListGrids that might account for this. I have also tried to replicate this warning on other similar screens in our application and have been unsuccessful thus far.

The fields listed in the warning are all part of the primary key of the DataSource that the lower ListGrid and ValuesManager are bound to. The full primary key includes only one other date field that's not listed in this warning. The first two fields are integer fields and the last two are text fields.

Please let me know if further information is needed. Thank you!

SmartClient Version: v12.1p_2021-06-05/Pro Deployment (built 2021-06-05)

[Isomorphic]

Not much to go on, but we would guess that this log is from the criteria system, and possibly has something to do with the criteria being prepared for the refreshData() call. What might be going on is that when the criteria was assembled, you used the same JS Object for both criteria, and/or possibly for some part of the data in the ValuesManager, so there is cross-talk between the components via modifications of these shared objects.

To fix your traceMessage call, just remove the "/"s - however, we'll modify that method to make it more flexible and clarify the docs.