This topic contains 4 replies, has 0 voices, and was last updated by JohnCCole 6 years, 6 months ago.

  • Author
    Posts
  • #18022

    Godrules500

    Is there any way, via scripting, to select an inactive entity (ex: Employee)? In this case, we are importing payroll information into a custom record. However, if an employee was terminated, they still need to get paid, so I need to be able to select the inactive employee in the dropdown field. Is there a way to do this via suitescript?

    Somehow enable an option that allows for inactive employees to be selectable?
    This is a cached copy. Click here to see the original post.

  • #18023

    Olivier Gagnon NC

    You will need to reactivate the employee, create the journal, then inactivate the employee. It is a fundamental NetSuite block to reject the the creation of new records referencing inactive employees, and scripting cannot bypass this.

  • #18024

    Godrules500

    Sad, that’s what I was afraid of. I was hoping to be able to get around it easily with a parameter in scripting. Thanks

  • #18025

    j.j

    this is a big bottleneck – we would not like to activate something in order to import or correct some data – e.g. resigned employees may need to attached later to other expenses etc. – unfortunately – we cannot do this from UI or through CSV or not even through coding. big limitation. there should be a switch to toggle records atleast while importing or programmatically

  • #18026

    JohnCCole

    While this on the surface is a definite annoyance and bottleneck as others have indicated. Could this not be overcome with a customization.

    At a really over simplified example could you build your own dropdown list of employees based on a search which could include inactive employees. Now that you have the id or name of inactive employee you could update the employee record to be active then attach that employee to the records you want and then inactivate the employee at the end.

    It wouldn’t make sense to create a customization when the issue happens a couple of times a year but if it was more frequent and the process flow was consistent it might be worth it for the business users.

You must be logged in to reply to this topic.