x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 138 subscribers
  • Views 785 views
  • Users 0 members are here
Browse Forums
Announcements
236
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
210
topics
416
replies
Sage Intelligence Reporting
121
topics
322
replies
Michael LeClair

Import template for Sales order with UDFs. UDFs on sales lines not being saved.

SOLVED
Posted By

Hi Everyone,

I was just wondering if anyone else has experienced this issue.  Basically, I've created three custom UDF fields on the sales header (SORDER) and detail (SORDERP). I've included those fields on both the header and details of the import template.  When I run the import, the sales order is created without error, but the UDF fields on the sales lines are blank (UDFs on the header are populated correctly).  As a test, I've replaced the line UDF fields in the template with base Sage X3 fields (Ex: ITMDES) and the same file will import with all fields properly populated.  There are no error messages in the response.  I ran an SQL profiler and the SORDERP.UDF's are included in the insert statement but the values are blank.  Has anyone ever had this issue before?  Could it simply be a bug in Sage X3?  Thank you in advance for your help.

Mike

  • 0
    SUGGESTED

    Good day Mike,

    Did you place the customer UDF fields on the screen SOH4 as well? The import works as follows, reads the file into the table, loads tables content onto the screens for validations/record completion, then clears the tables and does the commit. 

    Kind regards,

    Regard Hulsbos

  • 0 in reply to Regard Hulsbos

    Good morning Hulsbos,

    Wow thank you very much!!!  I had put the UDF's on WK2ALL4.  I've added them to SOH4 as well and now the import works fine.  I have a lot of experience integrating with various ERP's but I'm relatively new to Sage X3 so I'm still learning the ropes.

    Thanks again for your help and quick response it is much appreciated.

    Mike

  • +1 in reply to Michael LeClair
    verified answer

    Good day,

    You're most welcome, we all start somewhere and these are things that you learn with time. Basic principle of the import template is that they always make use of your object template window/screens on importing. If you want to see which screens are loaded by which table, on the object, look on the environments tab, there is a section called imports, within it the screen and table mapping used during data transfer.

    Just a note, when adding UDF fields, always add them on the template screens, then validate the entry transactions to add them onto your user's screens. Otherwise every time you validate the entry transaction associated with those screens, your changes will be lost. Screens starting with a W prefix are generated screens from an entry transaction.

    Kind regards,

    Regard Hulsbos 

  • 0 in reply to Regard Hulsbos

    Awesome thanks a lot for that additional info!!

*Community Hub is the new name for Sage City