Community
Showing results for 
Search instead for 
Do you mean 
Reply

How to catch "invisible" company?

Tuned Listener
Posts: 38
Country: Poland

How to catch "invisible" company?

Hello!

I have a problem. I prepared plug-in to integrate other application data wit ACT! in both direction. When current user has no rights to see specific company my system try to add this company from other application to ACT! second time. I can’t set information about integration in other application. Is there any way to know if specific company (by name) exist in system even if current user cant’t see it? I use method actApp.ActFramework.Companies.GetCompanies(null); to get all companies.

 

Bernard

Employee
Posts: 1,163
Country: USA

Re: How to catch "invisible" company?

Your ActApplication will be bound to the user permissions for the currently logged in user, OLE also respects current users security role.

 

The only thing I can think of is a separate application that logs into the framework as a different user and passes back in the collection of all companies to check for duplicates. 

Matthew Wood
Act! SDK Support
Community Moderator
Nickel Elite Contributor
Posts: 937
Country: USA

Re: How to catch "invisible" company?

Matt is correct - any access means into ACT! via the SDK will honor the security imposed by the logged in credentials.   Just a clarification to Matt's post - you don't necessarily need a separate application but you do need a second handle to the database using the elevated credentials for your code. 

 

Check out the OLEDB examples in devnet downloads board - in your code you can spool up another DB handle there and query the DB as a user with admin access with very similar code as in the examples.  Make sure to keep your 2 DB handles separate and to close both of them in your code!.

   

 

 

Tuned Listener
Posts: 38
Country: Poland

Re: How to catch "invisible" company?

Thx
Tuned Listener
Posts: 38
Country: Poland

Re: How to catch "invisible" company?

Thx, I will try incorporate this kind of solution in future.

 

Best regards

Bernard