UDF with Business Object Data Source Not Working

SOLVED

Here is a weird issue with a UDF that I am hoping those bad boys of Sage, Elliott and Kent, can help me with, if not anyone else. Created two UDFs in Sales Order Entry. We wanted to know who the order writer was and carry it forward to invoice history. The data source for both would be the Business Object, select Sales Order and then User Created Key. The fields available would come from the sy_user table. So I selected First Name for one and Last Name for the other. When I create a Sales Order the UDFs are NOT populated as expected. Now if I were to use Custom Office and add the fields to the panel it does show the correct data, but I can't carry that forward to history. Anyone seen this before. Any thoughts.

Parents
  • 0

    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

  • 0 in reply to Kent Mackall

    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.

  • 0 in reply to BigLouie

    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?

  • 0 in reply to Tyler Christensen

    It is not possible to do that Tyler

  • 0 in reply to BigLouie
    verified answer

    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

  • 0 in reply to Kent Mackall

    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.

Reply
  • 0 in reply to Kent Mackall

    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.

Children
No Data