This topic contains 4 replies, has 0 voices, and was last updated by Olivier Gagnon NC 8 years, 3 months ago.
-
AuthorPosts
-
August 2, 2016 at 9:43 am #6269
dlindyWe are using OneWorld with 6 subsidiaries, each of which has at least one Department and Location some have several. I have created a custom field on the employee record which stores the employees default location and department and would like to auto-populate those values, if present, to the transactions that the employee enters. These are required fields on every transaction, but with the exception of few employees, can be defaulted by employee.
Looking for a simple suitescript 1.0 or 2.0 that will source the default department and location from the user/employee record and write it to the desired transactions subsequent to the entity sourcing (customer or project). This cannot be done via workflow. Thank you.
This is a cached copy. Click here to see the original post. -
August 2, 2016 at 10:36 am #6270
Olivier Gagnon NCWell if you use the standard Department and Location fields you can use the Role to default them on transactions. That would be much simpler.
-
August 2, 2016 at 12:13 pm #6271
zackb22Why cant this be done by workflow? Are you trying to add it to the lines on the transaction as well or in the main? You could have them set after field sourcing of employee and then set department and location based upon employee custom fields.
-
August 2, 2016 at 1:28 pm #6272
dlindyHello Olivier,
It appears you are correct and this issue is now closed for us. I was not ware that I could use the user Role, “Division/Location Restrictions” dropdown set to “None – Default to Own”. This issue now goes away. Ironically, I have discussed this issue with silver support when trying to solve this problem with a workflow and was told to do it via scripting because workflows could not source the information from the user record. Thank you so very much!
-
August 3, 2016 at 5:30 am #6273
Olivier Gagnon NCExcellent, glad that solved it
-
AuthorPosts
You must be logged in to reply to this topic.
