My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Chamej — Fri, 27 May 2022 15:53:42 GMT

Do you think the problem might be in my approval interface? Since the only value that it's not getting is the ID:

Maybe I need to fix the ID fields (highlited in the next screenshot)?

Because checking the tutorial, eventhough they are using a reusable interface and I'm not, they use a get by ID rule)

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Chamej — Fri, 27 May 2022 15:16:29 GMT

Right! So i did select in Output' tab record as target and still doens't work:

I'm sending more screenshots to you about the rest of the input/output config for my Task Event and my Update to Data Base:

Thank you sooo much for your time, I really appreciate it

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Mike Schmitt — Fri, 27 May 2022 14:54:08 GMT

Your screenshot is of the Inputs tab. You actually need to configure the value to be saved via the Outputs tab (like you were about to have in your own prior screenshot).

[quote userid="112510" url="~/discussions/f/process/24729/my-approval-task-duplicates-the-item-with-a-new-value-in-the-status-field-instead-of-udating-it-only-with-the-new-value-in-status-field/95631#95631"]in the target value for Results Propoerties in Outputs, i can't choose =pv!record as a target[/quote]

Can you clarify what you mean by this? I can see it as a dropdown selection in your pior screenshot. You just need to select it(??)

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Chamej — Fri, 27 May 2022 14:26:23 GMT

But in the target value for Results Propoerties in Outputs, i can't choose =pv!record as a target, since as you can see in my last screenshot, I can only select a target from the dropdown list. 😞
I've selected Taget: record from that dropdown list, and nothing changed.

This is a screenshot from my first Write to Data Story, where the item is added.

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

laurensw — Fri, 27 May 2022 14:09:16 GMT

Choose the same value as set in the input parameter value

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Chamej — Fri, 27 May 2022 13:56:32 GMT

you mean like this Mike? Sorry I've never done this before, I'm not sure of what I'm doing here

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

laurensw — Fri, 27 May 2022 13:51:48 GMT

Now set the correct process variable (the one that is missing its ID now) as target value.

Upon the next instance of the process model, your problem should be solved.

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Mike Schmitt — Fri, 27 May 2022 13:39:23 GMT

The highlighted output needs to save back into the in-process CDT PV.

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Chamej — Fri, 27 May 2022 13:11:01 GMT

Here you go!

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

laurensw — Fri, 27 May 2022 12:47:09 GMT

Your elaboration indeed fits my description. Can you share a screenshot of the Data Outputs tab of the first Write to DB node in your process?

We need to have the process variable registered as the result target.

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

Chamej — Fri, 27 May 2022 12:30:48 GMT

That makes sense, because when I create a new Item, it generetes an ID, I can see it in the record as shown in the first image, and also in the summary, as I show here:

So the summary interface works.
But then in the Approval Interface there must be some kind of mistake, because when I open the task to Aproove it, it doesn't show the ID:

I understand what you say, but i can't find the mistake, this is the process detail of this second test made:

So I guess I need to assign a value to the ID in the approval fase, and it has to be the ID of the item to be approved, but how can I do that?

RE: My approval Task duplicates the item with a new value in the Status field instead of udating it only with the new value in Status field

laurensw — Fri, 27 May 2022 12:16:56 GMT

The problem here is most likely that you lose the id of the record somewhere in the interface/process.

That is the reason why a new row appears; a new id is assigned to the updated version of the already existing record upon saving to database.

Therefore I suggest check each step the data flows through in order to see where exactly the id of the item is lost.

My guess: it is the first write to DB node at which the variable is not mapped as data output result. If so, the initially written ID is not returned in the process variable.