To get around the last logged into site, create users like DMT_Site1 and DMT_Site2 that only have access to that specific site and use those users to log into DMT.
Yeah…that’s a thought. Kind of a pain with SSO. I mean, I have a non-SSO instance, but even in separate client install folders, the DMT still likes to single-sign-in anyway to the SSO instance (as me).
I’ve witnessed it before. Since it’s using the business logic - which I assume checks the current site - things that you couldn’t do without being in that site, would fail.
I mean I can’t even look at a Packer created in another site, with the Cust Shipment Tracker.
Yeah, and while that is mighty annoying, I can at least customize my tiles to open in a specific site. Can’t do that with DMT.
Of course, it’s not like I want to make a version of every tile for every site. I think you had a post about that a while back, choosing open-with for a specific site, or something.
And here’s a fun one I just found. I used DMT to make 330 customer shipment headers. Apparently I was logged into the other site. Can I change the Plant on those shippers? Nope. Can I add lines for a different site? Nope. So I’ll have to delete them all and try again.
I don’t know if I could have loaded these into the other site the first time, but if so, I sure wish Plant was required.