You are viewing limited content. For full access, please sign in.

Question

Question

Insert Data activity no longer outputs identity token after column is added to table and activity is "refreshed"

asked on October 30, 2018

We have a table that has an ID column. When workflow inserts data to it, we have it outputting the identity as a token so we can assign it to other objects.

We added a new column to the table recently, and then did a "refresh" on the Insert Data activity. The problem is now the Designer has forgotten about the identity token, despite the fact that it is checked. Existing tokens are underlined with red, and the Designer complains about not being able to resolve them when we publish.

The column is still set as identity in SQL:

How do we resolve this? Workflow 10.2

0 0

Replies

replied on October 30, 2018

Ege,

I ran into the same issue recently and my workaround was to uncheck and then recheck the Create Identity Token checkbox in the Insert Data activity after the refresh.

0 0
replied on October 30, 2018

I actually tried that and it didn't work.

It also doesn't work if I add another Insert Data activity and point it at the same table.

0 0
replied on October 30, 2018

Strange! 

I can duplicate the issue in Workflow Designer 10.2.0.216.  Any time I refresh the table in the Insert Data activity the identity token becomes unavailable in later activities.  But I can uncheck/recheck the Create Identity Token to make the token available again.

Even stranger is that when I add a second Insert Data activity with its Create Identity Token checked I do not see that second identity token in any later token dialogs!

Definitely something buggy going on...

0 0
replied on October 30, 2018

I am hoping this is a Designer bug and the server is actually able to resolve the token. Otherwise we're about to receive lots of support calls... sad

Hopefully someone from LF can comment soon.

0 0
replied on February 12, 2021

You may have to test the activity before it recognizes that it's outputting an identity token.

In the worst case you can use a custom query and this syntax:


INSERT INTO [LF_AffordableHousing].[dbo].[project]
(
       [row1]
       ,[row2]
       ,[row3]

)
OUTPUT INSERTED.[id]
VALUES 
(
       @row1
       ,@row2
       ,@row3
)

... which is how I've been solving this issue until I literally just saw the "Create identity token" checkbox

0 0
replied on February 12, 2021

This issue was fixed for Workflow 10.4.2. Reference ID 124899.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.