Unfortunately, that’s not possible/supported. The only way to sync/duplicate the db id-s in the MWS database is to either clone the entire database or migrate it via the migration tool, which will preserve these ids. The db id is dynamically assigned integer to a new “thing” in the MWS taxonomy (i.e. user/role/portlet/task/security policy/rule, etc.) and you can’t really rely on that. The solution here would be to give that portlet a proper alias, which is environment independent and can be transferred via webMethods Deployer or some other way. That would ensure that the same portlet is loaded in the other MWS env, without having to think about the exact db id.