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
Hi Guys,I have the following table structure on the request screen. There’s a parent-child relationship between order lines and claims. These two custom tables are connected as follows, I can add/edit records to the claims section without an issue.Now, I need to add the claims table (c_po_line_claims) under the tasks tab of the same request screen. But this time the connection is made via different fields.For this I created an alias of the c_po_line_claims table and made the connection as following. The data is filtered correctly. But when I try to update a record (ex: change the amount and save), I get the following error. It’s trying to run an update on the alias table, which is not an actual table in the database. Hence the error.I guess I’m missing something trivial. Any clues?
Hi experts,A pretty trivial question. When we do a clone from a prod environment to a dev environment, will this only copy over the data and leave the config changes in dev (ex: Custom metadata, UI , client script changes which are not applied to prod yet).If custom metadata A (which is in dev but not in prod) has the associated db table deployed in dev db, will this db table still be available in dev after a clone from prod?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
