Skip to main content
Solved

Create User in AD fails with error "Cannot read propety 'trim' of undefined

  • February 20, 2024
  • 3 replies
  • 112 views

Forum|alt.badge.img+1

I have been troubleshooting for days to find out why I can't get my workflow to work. I basically followed the sample use case provided for the App. I have tried using placeholders and I have tried creating a user with static information.

The ‘trim’ function should be something that removes whitespaces of variables, but here it claims that it is “undefined”. Yet I have filled in everything, tried it with blank fields, all filled in, you name it, I tried it.

The error code is so vague that I really don’t know where it goes wrong. Is this on the level of AD? Does the request even leave the webapp? Execution logs are also extremely vague, so I’m absolutely clueless here on what is going wrong...

Best answer by RMG.TDA

Hello Zach, the eventual reason will remain unknown but I’m taking a gamble it had to do with our testing environment was completely shielded off in a seperate network which caused multiple issues with the Orchestration Server communicating from the webapp to the test DC.

I don’t have the issue on production and everything seems functional now, so this thread can be closed.

Thanks for the support.

View original
Did this topic help you find an answer to your question?

3 replies

zachary.king
Skilled Expert
Forum|alt.badge.img+16
  • Skilled Expert
  • 951 replies
  • February 21, 2024

Hello @RMG.TDA, we are going to need some additional context to help you. Can you share the workflow? What value are you trying to trim? One thing you can do before you try and “Create the AD User” is take the value you are trimming and add it as a “Note” to a ticket. This will show you the exact value you are passing to the AD orchestration application. This is the best way I have found to make sure any interaction with placeholder values produces the correct result.

Give it a try and let us know how it goes. Take care!


Forum|alt.badge.img+1
  • Author
  • Top Contributor
  • 4 replies
  • Answer
  • February 22, 2024

Hello Zach, the eventual reason will remain unknown but I’m taking a gamble it had to do with our testing environment was completely shielded off in a seperate network which caused multiple issues with the Orchestration Server communicating from the webapp to the test DC.

I don’t have the issue on production and everything seems functional now, so this thread can be closed.

Thanks for the support.


zachary.king
Skilled Expert
Forum|alt.badge.img+16
  • Skilled Expert
  • 951 replies
  • February 22, 2024
RMG.TDA wrote:

Hello Zach, the eventual reason will remain unknown but I’m taking a gamble it had to do with our testing environment was completely shielded off in a seperate network which caused multiple issues with the Orchestration Server communicating from the webapp to the test DC.

I don’t have the issue on production and everything seems functional now, so this thread can be closed.

Thanks for the support.

Absolutely! Glad we were able to help, and you were able to find a solution :)


Reply