SD Behaviours executing off of the wrong ID

Whenever someone tries to add a Service Desk/Request Type mapping to a Behaviour and their project's servicedesk ID and viewport ID don't match, the Behaviour will be applied to a different project instead.

Here's an example:

Imagine there are two projects, Project A and Project B. Project A has a servicedesk ID of 13 and a viewport ID of 12, while Project B has a servicedesk ID of 14 but a viewport ID of 13. When you try adding a Service Desk/Request Type mapping to a Behaviour for Project A, the Behaviour will actually be applied to Project B instead. Because of this, it's possible that we are somehow inadvertently mixing up the servicedesk and viewport IDs when deciding whether or not to execute a Behaviour in the customer portal.