Skip to main content

Hi Experts,

We are running into this annoying error that completely locks down the task and prevents any update.
 


Above is when I tried to update the description field of the task 17525. This field is not associated with any business rule. In this example, this only occurs for the highlighted task 17525 whereas the other tasks can be updated without an issue. Also, I could update the task 17525 via SQL without an issue, so only an xml update seems to be causing this.

So, we suspect a certain pattern of processing the task ends up in causing the task to be in this corrupted state. Our current suspicion is that when we at once trigger multiple integrations that update the task, it leads to this (we are yet to ascertain that). But my contention is that it shouldn’t leave the task in this type of a corrupted state regardless of the process.

What I have since attempted is to mark all the custom metadata fields as “force select”, refreshed cache, re-logged in and tried to update the task. But it still throws the same error regardless of the field I update on this task.

Has anyone run into something similar before? Is this a bug? Any ideas?


 

@mmalek 

Hi,

 

This could be caused by many different things. I have seen this before, one cause was an change to the mask of a field to be capitals after data was already existing. So when it was displayed on the screen it would update the value in the field to all caps but the database record would still only have it as non-caps so it would see this a change after the record was selected, but that is just one reason why this error could happen.

Do you get this error if you try to update the description from the screen? What happens if you open the task and then move on to another task, do you get the message asking you to save changes?

 

Thanks,

Morris

Hi @mmalek 

Does your solution include manipulating the data with SQL script?

Cheers!

@Morris @Shneor Cheshin 
Yes, whenever I tried to update any field on that specific task, via web client/smart client, this error was thrown. And yes, when I try to move to another task it asks me whether I want to save changes. There are no client scripts connected to this action.

 Having said this, something really weird happened. I tried to do an update via the xml poster and it went through (changed the task owner),
 


Since then, the issue disappeared and now I can do changes to that task on the screen😮. I’m scratching my head for an explanation 🤕

@mmalek 

A glitch in the matrix 😎

Let us know if you find anything or have more questions.

Cheers!

Reply


Terms & ConditionsCookie settings