cancel
Showing results for 
Search instead for 
Did you mean: 

Change usersign2 for DI-API changes

0 Kudos

Dear all,

I'm currently building a C# application that is going to make some changes to some service calls. This application is running on a server with a single user id.

Now I need usersign2 to be the user responsible for the changes, and not the user for the application. This so when I view the servicall history I see the proper username.

I know that some company's are able to do this. At least some showed me they could do this in demos but their apps don't have everything we need, so hence the self build. Do they use DI-API to do so (if so, I can't find how), or are they secretly using SQL commands?

The end result I'm hoping for would be;
An application that is monitoring our GPS trackers.
Than updating the servicecalls when a technician (assignee) arrives and leaves.
I want to be able to to view these changes in the history log, BUT to have the update by hold the name (ID) of the technician (instead of the username the app is logged in with)

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

This is very unfortunate we have the same problem. Need to update UserSign and is not possible. SAP=HarlyDevidson... expensive and noisy but doesn't go.

0 Kudos

Nobody has any more info on how other companys that sell integration to B1 solve this?

0 Kudos

Hi Diego,

Thanks for you responce!

This really makes me wonder how some company's do manage to get the proper ID in those fields.

They have 1 single service running that is connected using the DI-API. This is using a single login, and yet in the history logs it shows the proper name (thus the proper ID in usersign2)

former_member185682
Active Contributor
0 Kudos

Hi Neeskens,

Is not possible to update the field UserSign and UserSign2 with DI API. This field is controlled by SAP and is defined with the user that made the action as you said.

What you can do is create a UDF on your ServiceCall and fill it with the id of your technician, but will not be able see this field in a default way in history log.

Kind Regards,

Diego Lother