Louie,

Not sure this fits your need but instead of trying to add the name of the user as UDFs, why not just map the UserCreated field from the Sales Order to the SO Invoice to AR History and then using that value to display the user in AR_History?

I did a quick test and was able to use the SO Sales Order Header user created key as a UDF in SO Invoice header and post it all the way through to AR Invoice History.  Now, I didn't translate in AR History into first and last name but you know how to do that.

If that doesn't fit the need, post back with more details.

Thanks,

Kent

Yes that sorta works but you don't get a name you get the three (3) digit User Code and not everyone will be able to realize which name goes with which code. That is why I was trying to get the name.

BigLouie,

If you have the UserCreated user code mapped into AR Invoice History, then can you find a way to add the SY_USER table to the panel and link it via the UserCreated User code and display the User First Name and User Last Name from SY_USER?

BigLouie,

If you have the UserCreated user code mapped into AR Invoice History, then can you find a way to add the SY_USER table to the panel and link it via the UserCreated User code and display the User First Name and User Last Name from SY_USER?

It is not possible to do that Tyler

Louie,

So what I outlined doesn't quite get what you want because you get the User Code and not the user name.  What if you post that all the way through to history and then use the user created key that is written to Invoice history in a script to read the user table and get the name.  You would need to add a UDF or two to invoice history header to display the name and I think it would be a Table Post-Read script to read the UDF that holds the key inofrmation and use the SY_User_svc object in the script to get the user record and return the user names.

Thanks,

Kent

I don't know if this will help but our sales people use the sales order history file to view historical information.  You can right click on the sales order and view the file info which includes the user created id and name.  If you can get by with using the sales order history file instead or AR history that might be a work around.  

I'm not sure why the created field is blank in the AR invoice history header inquiry.

Kent, I'll end up writing a script but I thought I could do it with the UDF but was curious why the field would not populate.

Once I figured out how to do the GetChildHandle the script worked just fine.