This content has been marked as final. Show 6 replies
It seems the error is because of the criteria you have selected. please delete the criteria and try to save it. if it is not saved, then problem with the data values entered in the top block.
FYI: criteria is to select the documents by giving Received DCI/DCM details, we cannot create the criteria with response values.
Please get back to me if you need any furhter info.
It seemed that this problem was going to go away on its own as we ceased to need the mass change. However, it has arisen again.
I have no problem creating a like set of criteria using responses. It is only when the special character is included in the filter that the error appears. It is somewhat odd as the character renders correctly in other areas of the interface, however, I begin to wonder if isn't still fundamentally a characterset issue.
Despite the efficiency of using the special character in the sql statement, I think I will need to simply define the change in another, probably more laborious manner to correct the problem.
Any further ideas are welcome.
Thanks for the suggestion. I don't think the length of the new response is the issue. My reason for this is that the error occurs before I've even defined this. Also, when I use a successful, but more belabored criteria, I am able to effect the change regardless of the relationship between the original and new values.