Inserting SQL row - increments the ID that I am parsing by random values

[SteepM]

Hi,

I have a flow that from webhook json body, I extract values and want to insert row in SQL Server Database. I had many successful tries, but when I started setting up correct Keys and relations, I realized that the ID that I am parsing which is 15-16 digits number, is changed after it is Inserted as a Database row. 

So this is the flow: 

And this is the Input for ID from a recent Successful run:

THIS IS THE OUTPUT OF ID AFTER INSERTION:

As you can see only the last digit is changed. I tried so many things, and I can't think of any way to solve this. Also, on other Tables and other Flows, it is happening the same, the ID that I input is modified for + few digits. 

Please share any info, Thanks!

[Pstork1]

What is the definition of the column in SQL?  Is this an Identity column in SQL?  If it is then SQL will generate a new number to make sure its unique.  For this to work correctly the column needs to be a Nvarchar column.

[SteepM]

It is the PK Column named ID as a bigint. 

I changed it to nvarchar column as you mentioned but still did the same thing.
INPUT:

OUTPUT:

[Pstork1]

I don't think you will be able to set the Primary Key for a record in a table.  What you want is a Foreign key to an external table.

[SteepM]

Then what is the usual way of inserting a row and keeping track of the ID? 

In the Insert a Row flow, this is a required field. .

So I need to provide an ID, but then how would I keep track of the right Primary ID/key when the one that I am providing is being modified after insertion in a very weird way, only the last two/three digits are modified from a 16 digit number.

[SteepM]

I also tried:

Updated the PK to Identity Column

Applied set identity insert to ON as explained in the docs. 

I now tried to insert a row with an ID: 9497000000553110

From the output: The returned row after insertion now has ID: 9497000000553111

[Szabi1983]

Have the exact same problem! Has anything changed so far?

[SteepM]

Not that I know of. It's really weird for me, and please if you get it working let me know on this topic.