Incident creation by inbound action in domain separated environment is created in wrong domain.

[Chandler2]

So, I see a MSP (Domain Separated instance). 

I see couple of inbound actions, all created in Global domain.

Now, the inbound action gets processed and creates an incident in a particular domain which is not correct as per client. 

The issue is that in the inbound action script, I don't see anywhere anything how it is setting the domain at all.

Any ideas where to look for?

Should I create inbound action in a particular domain if I want the incident to be created in that? 

Please help.

thanks!

#domain #inboundaction 

[Tony Chatfield1]

Hi, when you state 'not correct as per client' what exactly does this mean?
Have you checked
The configured domain of the inbound action
Content of the inbound action to see if it is applying a specific company\domain to the target record?
The domain of the user account that is mapped to the sending email address?

I expect the sending user would need to be in the target domain or have domain visibility of the target domain if the domain is not same as the users and is being set in script.

[Aditya24]

Hi Tony,

Thanks for responding. By wrong it means they're expecting it to be created in a different domain than what it was created into. 

The inbound action is in Global domain.

There is nothing in the inbound action script that I can see will set the domain. 

[Tony Chatfield1]

Was the task created in the dominion of the user/sender of the email?

If yes that would be expected behaviour.

Have you tried setting the correct company/domain in the inbound action?

[Community Alums]

Hi @Chandler2 ,

Check the user domain that created the records. Generally, the records created in the same domain which user belongs.

Please mark this correct or helpful, if this solves your query.

Thanks

Anand