We are in the process of testing to migrate from 2022 Client to 2024.2.9 in the browser. I have a user that has access to both of our companies. In 2022 she can create BAQs for both companies. She changes companies and opens BAQ designer and no problem. In 2024 in the browser she is in 1 company and opens BAQ designer and it comes in and says the company on the BAQ is the other one. What am I missing here?
The way it has always worked for me is that I CREATE all the BAQs in one company, then mark the ones used in other companies as All Companies (meaning all companies can run it). I can only CHANGE the BAQ in the company where it was created.
Prior to doing all the BAQs in one company, you could easily get into trouble by importing a BAQ into a different company (so that the same named BAQ exists for two companies). Then you don’t know which one will come up when you go into Designer. That has bitten me on the foot quite a few times. The cure to look at the owning company for that BAQ, switch to that company and pull it up there, export it, then delete it. Switch back to the correct company and import it there.
I don’t know if that is what is occurring for you, but I thought I’d share what I have run into before 
2 Likes
Thanks Marjorie for your reply. I think what you are describing is in fact a really good practice. However we have opened pandora’s box and allowed many end users to create BAQs. Some have access to both companies in our environment. I think what I am experiencing is in fact a bug in the browser version of 2024.2.9.
I guess if you were VERY determined (lol, I know) you could have someone go through and put them into one company, but yeah, it does make it more difficult when lots of people are doing them without a ‘rule’ about it.
I haven’t yet done anything with the browser version, in fact, I went through a great deal of trouble to get most things on classic screens because we have WAY too many customizations and very few users that could live in the browser. 
Yes it is a bug, I hope they fix it for 2025.1 release.
What I have found is if you use a mixture of the kinetic browser and the desktop client, it will hijack it based on the desktop client’s company.
Close the desktop client, then switch companies in the browser and switch back to the one you wish to use. I also utilize the company specific shortcuts on the menu in conjunction with this practice and it has seemed to fix my issues.